[osg-users] Memory usage with SubloadCallback

2014-11-25 Thread Cleo Saulnier
Hi, I recently upgraded from osg 2.6 to 3.2.1. I noticed that the SubloadCallback::load() now gets called exclusively and eats up all memory until the machine crashes. subload() never gets called anymore. I changed my Texture2D instance to use 1 mipmap level and forced it have zero levels

Re: [osg-users] Memory usage with SubloadCallback

2014-11-25 Thread Robert Osfield
Hi Cleo, There isn't any way I can determine what the problem from the information given. I can't rule out an OSG bug, but the only way to be able to find this out would be to have a compilable application that reproduces the bug so that I can test it first hand. It could very easily be a bug

Re: [osg-users] Memory usage with SubloadCallback

2014-11-25 Thread Cleo Saulnier
Thank you so much for your response! You saved me a LOT of time. I thought you had to call dirty() on the image associated with the texture in order for it to trigger the callback. Based on your comment that I was using both an image and a callback, I tried removing the image (which makes