There seems to be a memory leak in Vue 8. As I work a scene (which is pretty large) and modify various settings, resources are gradually expended until they drop into a critical area. For example, I generated a small ecosystem, changed the objects influenced by a light and shifted a camera angle. Resources fell to 52% and stayed there. I saved the scene, closed it and reloaded. Resources are now at 71%.

One the one hand, 71% resources free is better than Vue 7 for this scene. I just wish the resources wouldn't be used up by things that don't cost anything when a scene is saved and reloaded. 

IMO, Yes it does, and I reported it to e-on too!
Their response was "I'll pass it to tech".....in other words, "yes we know, thanks"
If they don't come back at you with a suggestion it means you're right and they know it.
Please log it with them, the more that do, the quicker it will be sorted [hopefully]!

 you have found the purge memory option haven't you?  that usually gives you back some of the memory before the resources start to fall again with the next thing you add or change.

thefixer, I wasn’t really clear on the specifics of the problem to the point where I felt confident to file a bug report. Performance varies. 

estherau, on a 64-bit system the purge memory feature doesn’t really do much. Sometimes I can get back 4%, sometimes not. 

• thefixer, I wasn’t really clear on the specifics of the problem to the point where I felt confident to file a bug report. Performance varies. 

• Yea, that's Vue for you though, if you have an issue, even if you can't accurately describe or repeat it you should still report it, it all goes to help with it's fix!

Esther: the purge memory is flaky at best, never worked sufficiently well in anything since Vue 6!

I'm not sure if it exactly has to do with memory leakage ...

If i work on a scenery and keep adding stuff, erase stuff, change scene settings and look, change atmo, exchange objects, add eco, erase eco, change eco, activate displacement, deactivate displacement and, and, and  - the resources logically will get lower and lower earlier or later.

The special things, Vue allows me to do, plus handling billions of polygons - i'm not sure, if it's that easy, to keep everything perfect clean in the memory organization. It must be pretty complicated, to write the code for the program, to do all that and the same time write routines, which suppose to decide, what's still needed or not. What should be kept in storage or not. Which parts of the scene, erased or not, are still related to each other.
And all that with endless possible given situations or scenery setups ...

That you will have your memory filled with certain things after a while working and changing many different or a few heavy impact details, is logical. And if i notice, that resources get lower, well, the cleanest way really is to save the scene (then only the scene related data will be saved) and restart (taking just seconds), to get the most resources back and use only what's needed.

And - i'm not sure, if they ever will be able to work out a perfect resources routine, which can decide by itself, what to keep or not to keep in memory ...
(Just let C4D, 3DSMax or whatever the big 3D packages are called, create and handle procedural terrains and special texturing and immense plant use - and keep their memory handling clean. Since they don't use special stuff like ecosystem and whatever Vue is specialized in, than those application for sure have an easier job, to handle their resources ... and make them look good, in whatever they can do ...).

Quote -  you have found the purge memory option haven't you?  that usually gives you back some of the memory before the resources start to fall again with the next thing you add or change.

Doesn't do anything at all on my system.  Didn't in Vue 7 as I recall.  Last time I had a working 'purge memory' was way back in Vue 6

My experience is that "purge" works the first time, but after that barely if at all and the first time it only gives back a small percentage.  I've seen leakage simply by changing materials on objects.  The first time you realize that the memory is dropping is when you get the "system resources has dropped below........" message  and all you've done is change materials yet object  size has never changed.   This particular leak has unfortunately been around for several  versions.

 gosh it works for me but sometimes I do it 2-3 times at a time, and then after the next change I do it again once or twice etc.
Love esther

I use Vue 8 Infinite 32-bit and I have to close Vue and restart it after each render if I want my resources back,.  Otherwise, I gradually run out of RAM.  The purge button does nothing to free up RAM or swapfile space.

 Yo are right, I do often have to close vue 8 and reopen it again to get the full capacity back.
Love esther

E-on fixed it in Vue 7.5.  So maybe they'll fix it again in Vue 8.5.

I rarely used 7.5 as I bought it a couple of weeks before 8 so I never checked.  It's uninstalled now.

I wonder if it's something to do with 64 bit because I tried with 6 but it didn't work even though it used to on my old 32 bit.  Also took a lot of effort to get the resources to drop below 70% which may be why it didn't work.   I need to try something that really eats resources to get it really low but was in a hurry.    If I'd put the same amoutn of stuff in 8 that Idid in that test though, it would have been well down.

I'm finding that moving stuff around a lot and twisting and turning etc. really starts to drop the resources big time, now where have I seen that before........Oh yea, Vue 6 when they screwed it up with an update that took Months to get another update in to sort it out!!

I managed to get 6 down to 44% resources this after' with a LOT of stuff in there and the purge did work even if rather feebly.

I tried to get 8 to drop down (very easy just edit a few plants!!) and it soon gave me a message about dropping to critical level.  Even then the purge didint'work BUT something that was very strange was that I did a quick preview renderof my newly edited trees and after that'd finished and closed out the resources went from 18% to 65% all on their little own.

Hmmmmmmmmmmmmmmmmmm

I haven't tried it yet.  But maybe rendering a scene with Preview just after rendering it with User Settings set high could return resources.

Maybe.

**"The special things, Vue allows me to do, plus handling billions of polygons - i'm not sure, if it's that easy, to keep everything perfect clean in the memory organization. It must be pretty complicated, to write the code for the program, to do all that and the same time write routines, which suppose to decide, what's still needed or not. What should be kept in storage or not. Which parts of the scene, erased or not, are still related to each other.
And all that with endless possible given situations or scenery setups ...

That you will have your memory filled with certain things after a while working and changing many different or a few heavy impact details, is logical. And if i notice, that resources get lower, well, the cleanest way really is to save the scene (then only the scene related data will be saved) and restart (taking just seconds), to get the most resources back and use only what's needed.

And - i'm not sure, if they ever will be able to work out a perfect resources routine, which can decide by itself, what to keep or not to keep in memory ...
(Just let C4D, 3DSMax or whatever the big 3D packages are called, create and handle procedural terrains and special texturing and immense plant use - and keep their memory handling clean. Since they don't use special stuff like ecosystem and whatever Vue is specialized in, than those application for sure have an easier job, to handle their resources ... and make them look good, in whatever they can do ...)."**

I have to disagree entirely.  Vue doesn't do anything "special".  It's math; it's instancing.  All of the major 3D packages have instancing, and none of them handle it as poorly as Vue does.  The high-end packages all handle memory better, especially at rendertime.  They can all handle far more vegetation than Vue.  And without bogging down or crashing.  AND, on top of that, while actually giving you the geometry you're working with instead of dodgy, nebulous wireframes that barely give you an idea where each plant is going to go.  You can even select ANY single vertex on ANY single leaf, or change the material of one leaf or all or just a few...  And proxies!  Vue doesn't even touch upon proxies, binary or otherwise.  And you don't have to restart them to get them back under control; you have full control of your memory allocation every step of the way, especially in Maya and Max.

Ecosystems aren't special at all; Maya for example has no problem painting massive plant systems on all kinds of geometry.   And also no problem handling huge datasets, billions of polys,  fractal procedural terrains or ANY kind of object, and ridiculously complex displacements.  And mental ray renders far, far faster and better than Vue's renderer, with full-on GI/FG, physcially accurate materials and caustics, and all kinds of other features.  I'm actually surprised E-on hasn't purchased MR as an optional renderer for Vue.

Simple example scene I've been working on (Maya viewport):

This scene isn't finished obviously, but a good example of vegetation-painting and instancing.

And if you want to see how realistic such scenes can get, check this thread at CGTalk:

http://forums.cgsociety.org/showthread.php?f=132&t=754315&page=1&pp=15

Example render (NOT mine, by the way!):

I'm not stating all this to say that Vue isn't a useful tool.  Vue is awesome and has MANY great features, especially when it comes to parametrics!  The skies are amazing; it takes much, much more work to make such skies with other packages.  It's much easier to start up and far easier to learn, of course.  But when comparing Vue to the major 3D packages, I just believe that you are inexperienced or uneducated on their capabilities.  There is nothing Max or Maya can't do that Vue can; there are millions of things that they CAN do that Vue can't.

Please take this post with a grain of salt... Just clearing up misconceptions; I love Vue too!

I just noticed something in Arraxxon's post that escaped me before. 

And if i notice, that resources get lower, well, the cleanest way really is to save the scene (then only the scene related data will be saved) and restart (taking just seconds), to get the most resources back and use only what's needed.

 It takes me seven minutes to save and restart the Tenochtitlan scene. Naturally, I would prefer it if Vue had better memory management.