Help with exceptions in VSDocumentManager needed

Hello everyone,

We constantly receive reports about exceptions in JetBrains.ReSharper.Editor.VSIntegration.VSDocumentManager
via ReSharper exception submitter. The latest examples are 23600, 23598,
23597, 23595, etc. Despite the manifest abundancy of such exceptions on the
EAP user machines we failed to reproduce one on our computers. So far, all
we know is that it happens when a file is being opened in Visual Studio (either
deliberately or through invoking some action that opens a file as a side-effect).
We plan to introduce additional logging in future builds to cope with the
problem. Just now we would appreciate any pointers on how often you encounter
that sort of exceptions and what usually preceeds them.

Thanks,
Andrey Simanovsky


4 comments
Comment actions Permalink

.... so if someone encounters this problem on a regular basis and notices
some pattern, such an information is very valuable to us.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hello everyone,

We constantly receive reports about exceptions in
JetBrains.ReSharper.Editor.VSIntegration.VSDocumentManager via
ReSharper exception submitter. The latest examples are 23600, 23598,
23597, 23595, etc. Despite the manifest abundancy of such exceptions
on the EAP user machines we failed to reproduce one on our computers.
So far, all we know is that it happens when a file is being opened in
Visual Studio (either deliberately or through invoking some action
that opens a file as a side-effect). We plan to introduce additional
logging in future builds to cope with the problem. Just now we would
appreciate any pointers on how often you encounter that sort of
exceptions and what usually preceeds them.

Thanks,
Andrey Simanovsky




0
Comment actions Permalink

After installing build 236 (including hotfix) I got this exception on about
every key press, R# but also other plug-in shortcuts. I submitted some under
23174, 23169 and 23168. Compare to see if that is what you mean.

I soon had to quit Visual Studio as it was unworkable. I discovered that my
C: drive was getting rather full (<= 400MB free space), so I split my
PageFile.sys over C: and D:, cleared the temp directory (including R#
caches!) and rebooted. Since then the exception is practically gone (had
only 2 or so of them since).

Hope this helps,
Erwin

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> schreef in bericht
news:c8a894d916018e8c836a52eacf0bc@news.intellij.net...

... so if someone encounters this problem on a regular basis and notices
some pattern, such an information is very valuable to us.

>

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>> Hello everyone,
>>
>> We constantly receive reports about exceptions in
>> JetBrains.ReSharper.Editor.VSIntegration.VSDocumentManager via
>> ReSharper exception submitter. The latest examples are 23600, 23598,
>> 23597, 23595, etc. Despite the manifest abundancy of such exceptions
>> on the EAP user machines we failed to reproduce one on our computers.
>> So far, all we know is that it happens when a file is being opened in
>> Visual Studio (either deliberately or through invoking some action
>> that opens a file as a side-effect). We plan to introduce additional
>> logging in future builds to cope with the problem. Just now we would
>> appreciate any pointers on how often you encounter that sort of
>> exceptions and what usually preceeds them.
>>
>> Thanks,
>> Andrey Simanovsky
>
>



0
Comment actions Permalink

Hello Erwin,

Yes, these are the same exceptions. Thank you for the response.

After installing build 236 (including hotfix) I got this exception on
about every key press, R# but also other plug-in shortcuts. I
submitted some under 23174, 23169 and 23168. Compare to see if that is
what you mean.

I soon had to quit Visual Studio as it was unworkable. I discovered
that my C: drive was getting rather full (<= 400MB free space), so I
split my PageFile.sys over C: and D:, cleared the temp directory
(including R# caches!) and rebooted. Since then the exception is
practically gone (had only 2 or so of them since).

Hope this helps,
Erwin
"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> schreef in
bericht news:c8a894d916018e8c836a52eacf0bc@news.intellij.net...

>> ... so if someone encounters this problem on a regular basis and
>> notices some pattern, such an information is very valuable to us.
>>
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Hello everyone,
>>>
>>> We constantly receive reports about exceptions in
>>> JetBrains.ReSharper.Editor.VSIntegration.VSDocumentManager via
>>> ReSharper exception submitter. The latest examples are 23600, 23598,
>>> 23597, 23595, etc. Despite the manifest abundancy of such exceptions
>>> on the EAP user machines we failed to reproduce one on our
>>> computers. So far, all we know is that it happens when a file is
>>> being opened in Visual Studio (either deliberately or through
>>> invoking some action that opens a file as a side-effect). We plan to
>>> introduce additional logging in future builds to cope with the
>>> problem. Just now we would appreciate any pointers on how often you
>>> encounter that sort of exceptions and what usually preceeds them.
>>>
>>> Thanks,
>>> Andrey Simanovsky
Thanks,
Andrey Simanovsky


0
Comment actions Permalink

We managed to reproduce the problem. We hope that the case we discovered
is the main (and only) cause of the problem.
Greate thanks for all who responded to the request.

Hello everyone,

We constantly receive reports about exceptions in
JetBrains.ReSharper.Editor.VSIntegration.VSDocumentManager via
ReSharper exception submitter. The latest examples are 23600, 23598,
23597, 23595, etc. Despite the manifest abundancy of such exceptions
on the EAP user machines we failed to reproduce one on our computers.
So far, all we know is that it happens when a file is being opened in
Visual Studio (either deliberately or through invoking some action
that opens a file as a side-effect). We plan to introduce additional
logging in future builds to cope with the problem. Just now we would
appreciate any pointers on how often you encounter that sort of
exceptions and what usually preceeds them.

Thanks,
Andrey Simanovsky

Thanks,
Andrey Simanovsky


0

Please sign in to leave a comment.