Re: [osg-users] StateSet setAttribute(Material) question

2010-09-21 Thread Robert Osfield
Hi Tom, I haven't heard of assigning an osg::Material as a cause of memory growth before, and what you are doing sounds like it's something that has been done with the OSG for over a decade, so my guess is that the basic should be working just fine. The three aspects that could be a cause are a

Re: [osg-users] StateSet setAttribute(Material) question

2010-09-21 Thread Tom Pearce
Hi Robert, I agree with your assessment of possible places to look. This occurs even with creating a single new Material, and I always use ref_ptrs, so that isn't the source of it. I'll look into drivers etc. and post anything I find here in case others come across the same issue. Anybody

Re: [osg-users] StateSet setAttribute(Material) question

2010-09-21 Thread Jean-Sébastien Guay
Hi Tom, Anybody out there have suggestions of a Windows process memory usage tracker that would be good to use? Try Process Explorer. In the process list, right-click on your app and select Properties, and you'll be able to see detailed CPU and memory usage graphs and stats specific to

[osg-users] StateSet setAttribute(Material) question

2010-09-20 Thread Tom Pearce
Hi OSGers, I'm using setAttribute(osg::Material* mat) on a matrix transform to control the color of an object (just a simple sphere for now, nothing fancy). Just using task manager in windows to watch process memory usage, I noticed that upon adding an object to the scene, the memory usage