4 comments
Comment actions Permalink

This turned out to be too many errors for me--up to every ten minutes when working last night. I uninstalled build 255 and reinstalled 254.

0
Comment actions Permalink

Hello Samuel,

I believe this problem can be remedied by simply removing ReSharper caches,
no necessity to rollback to the previous build (in fact, there
have been no changes that might affect this for a long time already). Concerning
the 'Don't show exception...' checkbox - it works, but only in the
case when the stack trace of the exception is identical to a stack trace
already seen in the current session. Unfortunately it is a common scenario
when the exception happens in a recursive call chain, and thus stack traces
differ in level of recursion, or in frames of UI message dispatching code.


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

This turned out to be too many errors for me--up to every ten minutes
when working last night. I uninstalled build 255 and reinstalled 254.



0
Comment actions Permalink

Thanks for the additional info. Does ReSharper automatically clear the cache when a new build is installed? Is it possible that cached data from a previous build is causing issues in 255? I just find it odd that this happens so much now that I installed 255 and never before. It also has not happened since reverting to 254 (although uninstalling resharper and reinstalling could have fixed it by clearing caches).

Thanks for the info re Don't show. Perhaps for situations where the stack traces varies so much, it'd be nice to have an option to not show exceptions ever, or at least until the next upgrade or for the rest of the session or something.

Best regards,

Sam

0
Comment actions Permalink

Hello Samuel,

yes, to the best of my knowledge installing a newer build effectively cleans
the cache by
simply making ReSharper to ignore its contents.


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

Thanks for the additional info. Does ReSharper automatically clear
the cache when a new build is installed? Is it possible that cached
data from a previous build is causing issues in 255? I just find it
odd that this happens so much now that I installed 255 and never
before. It also has not happened since reverting to 254 (although
uninstalling resharper and reinstalling could have fixed it by
clearing caches).

Thanks for the info re Don't show. Perhaps for situations where the
stack traces varies so much, it'd be nice to have an option to not
show exceptions ever, or at least until the next upgrade or for the
rest of the session or something.

Best regards,

Sam



0

Please sign in to leave a comment.