bigosmallm / papervision3d

Automatically exported from code.google.com/p/papervision3d
1 stars 0 forks source link

Another papervision memory leak #267

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Continuously create and destroy large numbers of polys

What is the expected output? What do you see instead?
Expect stable memory usage, instead we get a leak.

What version of the product are you using? On what operating system?
Papervision3D_2.1.932

Please provide any additional information below.

This can be 'fixed' - fudged would be more appropriate - by commenting out 
line 257 of the BasicRenderEngine.as file.

Original issue reported on code.google.com by d...@dev01.co.uk on 13 May 2010 at 4:01

GoogleCodeExporter commented 9 years ago
Further investigation suggests this might be me. I'll update when I'm sure.

Original comment by d...@dev01.co.uk on 14 May 2010 at 9:28

GoogleCodeExporter commented 9 years ago
are you talking about : 
viewport.lastRenderList.push(rc);

if so I would not comment it but find where to pop 
(viewport.lastRenderList.pop(rc))
when needded...

Original comment by damien.miras on 18 May 2010 at 11:14

GoogleCodeExporter commented 9 years ago
Hi,

This does still look to be me - I think I'm continually adding faces somewhere 
that require mouse hit 
detection. When I commented out the line I found that (duh) my hit detection 
stopped working - which 
dampened my initial delight at thinking the problem had gone :-P

I think the reason that this appeared to be the leak is that for some reason it 
really ramps up the affects of the 
leak. With that line commented out the memory usage did go up but at a much 
slower rate. This lead me back 
to the root of the problem which was in my code.

I think you could probably close this issue - but it might be something to keep 
an eye on.

Thanks!

Original comment by d...@dev01.co.uk on 18 May 2010 at 3:26