Looking more into my sudden development environment problem, Visual Studio 2010 appears to get stuck in a recursive memory eating loop as it tries to simply enumerate the resources of my solution for the resource view (showing an entirely blank resource view while doing so). Giving it time, it simply eats up all available memory. So, now I've got to revert to last night's solution and re-do any changes to the solution made since then -- hopefully without causing this strange recursive loop to occur again. My goodness Microsoft ;o. Under NO circumstances should that be allowed to occur.
UPDATE: This was verified to be the cause. Reverting ONLY my .SLN file solve the issue. Visual Studio 2010 actually saved my solution in a way that caused its resource editor to get stuck in a memory eating infinite loop. If this isn't a good example of why ProBalance is handy, I don't know what is, lol ;). Even the best (or not so best) software sometimes malfunctions.
Monday, 11 October 2010
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment