Target from the installed shortcut (don't know whether this is a change):

"C:\Program Files (x86)\SecondLifeReleaseCandidate\SecondLifeReleaseCandidate.exe" --settings settings_releasecandidate.xml --channel "Second Life Release Candidate"

No items checked on the compatibility tab for the shortcut. Also none noted for the program itself.

After reinstalling, when I allowed the viewer to start, windows display settings were reverted to the Basic theme.

If you have, please attach a crash report

Knowledge Base > Second Life Info > Solution Finder > Technical Issue > Where do I find my Second Life diagnostic logs? Topic #: 4051-4209
http://secondlife.com/support/?questionID=4209

Thank you

I have yet to encounter the Program Compat. message shown, following a crash of RC 1.20.8. The general memory issue does continue to exist, but the leakage seems to have (perhaps) slowed significantly? This is a subjective statement, as I have not timed the most recent crashes at all rigorously.

Also hard to say, as I have been using several other builds lately in addition to the 8th RC build. The general memory leakage seems to lead to similar crashes once the heap hits the 3GB wall in most all of the viewer builds I've tried, but in most cases it takes long enough that I am often not present to determine the time of the crashes or note enough similarities between them to warrant a report that might be helpful. Will keep your request in mind for next time, though (assuming I manage to crash again before the next RC is released). I think I will downgrade this to Normal, as the issue is now more of an occasional annoyance than something that regularly interrupts content creation efforts or other functions.

Changed Priority to Normal, as per your request. One of the main issues re memory, VWR-6851 , which you have commented on, is open and assigned. As the reporter of this issue, you may choose to resolve/close this as a duplicate and continue to comment on VWR-6851.

Actually, where I reexamined the Linden definitions for priorities, it was clear that this remained a Major issue. Downgrading to Normal was slightly too optimistic, as crashing still qualifies as Major, and, while the frequency is less, expecting users to keep an eye on the Task Manager for signs that SL is approaching a crash is probably not a realistic expectation, if LL expects average non-technical users to have any confidence in the viewer. Also, from anecdotal accounts in world, my present installation is far more stable than most of those I've talked to (where memory leakage sounds like it is still a big contributor it viewer instability).