I discovered something while writing a reply to this thread. I was starting to experience some strange instability with one of my N5.2.2 32-bit PC projects and last night I checked in Task Manager and took note that the memory footprint was over 2 gigs in size. It hadn’t crashed, but screen redraws were slow, sometimes I had to wait a while because the keyboard wouldn’t start playback, and there was some other oddities going on in the editors. I was going to slim it down first thing this morning.
After reading this thread, I started N5-32 to see what the base memory footprint was. It was 172 megs when the loading stops, but it doesn’t stop growing: it keeps incrementing by 256k every 8 seconds or so.
After loading last night’s project, it used 1.638 gigs. Last night it was well over 2 gigs in size when I stopped working. And the 256k incrementing continues after the project is loaded without any other activity on my part.
It could be Nuendo, or it could also be something Nuendo pre-loads, like Waves’ Waveshell, media player, etc… I don’t know for sure, but this doesn’t seem normal to me. Looks like it could be a memory leak.
This would make a case for stopping work every couple of hours to save, quit Nuendo, restart Nuendo and reload; that might be a stopgap solution for now for avoiding corruption in 32-bit projects. But if this in fact the problem, then how close your project sits to the max mem limit of a 32-bit project will determine how much time you have to work.
BTW: What is the EXACT memory limit of Nuendo 32-bit running in Windows 7 64-bit?