Closed mrksfnk closed 12 years ago
I must admit that this type of error-posting looks very messy but how can I improve that? Is there a possibility to upload files? Is there a seperate bug tracker?
It's messy but it's extremely informative :). I think you could upload the error message itself into a gist and then link the gist to this bug.
As for the actual bug this is the second report I've seen of this. The problem is one of the COM components in Visual Studio is incorrectly returning E_OUTOFMEMORY. I say incorrectly because it's very unlikely that we are actually out of memory here. I haven't been able to repro this locally so it's been difficult to track down what the root cause is.
As a temporary work around I'm going to just treat this as a misbehaving COM component and catch the exception. I'll try and upload a patch later tonight.
What all extensions do you have installed on this machine?
OK that sounds fine, so I made an update on my post containing a link to a gist.
My other extensions on this machine are:
Submitted a fix for this just a bit ago. Going to be releasing a patch tomorrow sometime which will include this patch. I'll post a link here when I release it
a9d70aba5c6b4ed2c7337f45aad788d78e8977dc
I have to admit that VsVim never worked correctly or even just worked. For example the option dialog was always empty for me and the _vimrc file was not read, although the same configuration worked for me at my home machine, it does not at my working machine. Can this be due to limited user rights?
Here's my VS10 Log. I have extracted only the entries that contain VsVim:
git://gist.github.com/2234509.git