Today, changing the ID of a view caused an "Access violation" invalid memory read operation at address FFFFFFFFFFFF..."
Probably the change of ID is not the cause but there's a memory leak/wild pointer/etc somewhere in the code.
I had been doing a whole bunch of things before that: the whole calibration/registration/integration ordeal on a LRGB set, BN, DBE, histogram, ACDNR, color saturation, etc. Not sure if it's worth mentioning it, but the very last two steps were a dynamic crop, ID change and histogram transformation. Then a new ID change and bang! My system was reporting 11.01 GB of RAM in use and 7.41GB free, so not a memory full issue.
I had 18 other apps also running - some tiny, like 4 Notepad sessions, NetTerm and stuff, others not so tiny like OpenOffice, Firefox, MS Visual Studio, Photochop, etc). None affected.
Funny thing is... I'd OK the error and it'd happen again right away, and again, and again, forever... But between each exception error there was a lapse of maybe 1/4 of a second, and that allowed me to click the Save As icon and save that image. Then, between that interval, click on another image... then the exception error would stop showing up. Clicked Save As, saved that other image, then, error popped up again, and again, but now not right after... In fact, now the "pauses" between the errors could last a minute or more... which allowed me to use the new SAVE WHOLE PROJECT feature to save PI's current state of affairs. Oh wait, that's not implemented yet... What was I thinking!!
The moment I would shift focus to that first image, the error would start popping up again.
This is on Win7x64, v1.06.09.0652 c86_64
