| Author |
 Topic  |
|
|
st80rules
Junior Member
12 Posts |
 Posted - Jun 17 2008 : 2:50:33 PM
|
Hi,
since going to build 1640, I've been getting the infamous deadlock, where one or more IDEs show "VA X: Waiting for other instance of Visual Studio to flush DB..." and one IDE going crazy with memory (usually eating up 1.5 Gb of VM).
Let me know what info can be of value. I can't reproduce it at will, but it eventually bites me.
Normand |
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Jun 17 2008 : 6:05:13 PM
|
Can you try to exit all instances of Visual Studio, and then do the following:
VA Options -> Performance -> Clear history, cache and temporary files
and
VA Options -> Performance -> Rebuild symbol databases
and then restart Visual Studio.
Eating a lot of RAM can happen because of corrupt symbol databases.
About instances: do you working on different versions of the same project, or on totally different projects?
Which Visual Studio do you use? |
 |
|
|
st80rules
Junior Member
12 Posts |
Posted - Jun 17 2008 : 9:59:50 PM
|
I have already rebuilt the symbol databases, so the problem is gone for now. Note that I have to end the IDEs with the task manager in order to exit this deadlock when it happens.
I work on 3 or 4 different projects, with Visual Studio .NET 2003 (version 7.1.6030). |
|
|
|
feline
Whole Tomato Software
United Kingdom
18996 Posts |
Posted - Jun 18 2008 : 10:52:24 AM
|
We have made some changes to how the symbol database is handled internally, to try and stop this happening. Hopefully these changes will show up in the next beta build of VA.
Does this problem seem to be worse in VA 1640? If so it might be a good idea to try a slightly older version that seemed to cause fewer problems for now. |
zen is the art of being at one with the two'ness |
|
|
|
st80rules
Junior Member
12 Posts |
Posted - Jun 18 2008 : 11:48:31 AM
|
| Yes it seems to be worse in 1640. My previous version was 1632 and it seemed to be more stable in regards to this problem. |
|
|
|
feline
Whole Tomato Software
United Kingdom
18996 Posts |
Posted - Jun 18 2008 : 3:41:11 PM
|
I am not aware of any changes that would have made this worse. Apologies for this.
For now the solution is to either roll back to VA 1632 (you can simply install over the top of 1640) or just keep rebuilding the symbol database by hand until the next version is available. Hopefully it will help. |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
Deadlock between IDEs
