|
strange leakWhile fixing a massive leak in _1024_MATHstructure plugin, i noticed that the GeforceGLdriver seemed to be leaking as well. I checked with instruments, monitoring a simple QTZ (a moving white sprite, no plugins used), and the GeforceDriver is still leaking..... Am I right to freak out ?
|
note : I'm on a MBP 2009/ geforce9600M / 10.6.4
That's interesting and worrying at one and the same time :-)
I found a strange issue - maybe driver issue - while rendering in MSAA+FBO, so i think 10.6.4 nVidia drivers are bad. I have the same config.
10.6.4 related only ? Hopefully my live-performance machine is 10.6.1 .... I'll check that this week end.
Yep, with 10.6.3 everything worked fine. BTW, many users discovered issues with 10.6.4 GL drivers, googling "10.6.4 opengl issue" and will find a lots of posts.
Yeah you are. Last night I was doing something and noticed my startup disk filling up. Crapppppppp.
I don't know if I'd classify it as a "massive" leak -- from what I've observed, it leaks ~200-300 bytes per context created. So unless you're creating/destroying tons of CGLContextObj's, it shouldn't be too severe (there may be other operations that cause it to leak too though? If so, I'd be interested to know what they are). I think it was present on 10.6.3 as well (and possibly even earlier; I've not really checked anything before that)
That said, it is pretty bad if you are doing that. It threw off some of our test results.
If you do something where you have to use a queue inside of an iterator, it seems like in certain scenarios that it can cause a massive leak. I'll try to home in on it more...
That one may be a QC leak -- there are quite a few of those, unfortunately. It's the nvidia driver ones that are scary (because they cannot be worked around, and affect every GL-using app)
If creating/destroying tons of CGLContextObj's means enabling/disabling tons of GL_consumer patches, then yes.... After 4mins i got a 1MB+ leak.
Note that the observed leak is present only when working within the QC editor, not on my compiled app (using QCviews). I guess that's not too bad.