I hate this error JetBrains

Is there a way to ignore all exceptions without that dialog window popping up? Errors every 2nd keystroke in the source view of an aspx page is very aggravating.



JetBrains.Util.LoggerException: Exception of type 'System.OutOfMemoryException' was thrown. ---> System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parsePrimaryFollow(CompositeElement primaryCandidate) in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 222
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parsePrimaryExpression() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 557
   at JetBrains.ReSharper.Psi.CSharp.Gen.CSharpParserGenerated.parseUnaryExpression() in c:\Agent\work\e9a2fff71e84fb33\src\Gen\Parsing\CSharp\CSharpParserGenerated.cs:line 21303
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseExpressionMul() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2173
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseExpressionAdd() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2442
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseExpressionShift() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2414
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseExpressionRel() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2370
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseExpressionEqu() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2343
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseExpressionAnd() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2321
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseExpressionEor() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2299
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseExpressionIor() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2277
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseExpressionCand() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2255
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseExpressionCor() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2233
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseExpressionNullC() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2210
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseExpressionCondOrAssn() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2562
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseCSharpExpression() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2149
   at JetBrains.ReSharper.Psi.CSharp.Gen.CSharpParserGenerated.parseExpressionStatement() in c:\Agent\work\e9a2fff71e84fb33\src\Gen\Parsing\CSharp\CSharpParserGenerated.cs:line 9541
   at JetBrains.ReSharper.Psi.CSharp.Gen.CSharpParserGenerated.parseDeclarationOrExpressionOrLabelStatementInternal(CompositeElement result) in c:\Agent\work\e9a2fff71e84fb33\src\Gen\Parsing\CSharp\CSharpParserGenerated.cs:line 7489
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseDeclarationOrExpressionOrLabelStatement(CompositeElement result) in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 708
   at JetBrains.ReSharper.Psi.CSharp.Gen.CSharpParserGenerated.parseStatementAuxInternal(CompositeElement result) in c:\Agent\work\e9a2fff71e84fb33\src\Gen\Parsing\CSharp\CSharpParserGenerated.cs:line 18671
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseStatementAux(CompositeElement result) in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 1221
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.parseBlock() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 2746
   at JetBrains.ReSharper.Psi.CSharp.Parsing.CSharpParser.ParseCodeBlock() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Parsing\csharpParser.cs:line 67
   at JetBrains.ReSharper.Psi.CSharp.Impl.Tree.ChameleonBlock.<OpenChameleon>b__0(IParser parser) in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Impl\Tree\ChameleonBlock.cs:line 87
   at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.ChameleonElement.Parse(ParseChameleonElement parseFunc) in c:\Agent\work\e9a2fff71e84fb33\src\Psi\src\ExtensionsAPI\Tree\ChameleonElement.cs:line 38
   at JetBrains.ReSharper.Psi.CSharp.Impl.Tree.ChameleonBlock.OpenChameleon() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Impl\Tree\ChameleonBlock.cs:line 87
   at JetBrains.ReSharper.Psi.CSharp.Impl.Tree.ChameleonBlock.get_FirstChild() in c:\Agent\work\e9a2fff71e84fb33\src\Psi.CSharp\src\Impl\Tree\ChameleonBlock.cs:line 39
   at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants(IRecursiveElementProcessor processor) in c:\Agent\work\e9a2fff71e84fb33\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 110
   at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants(IRecursiveElementProcessor processor) in c:\Agent\work\e9a2fff71e84fb33\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 116
   at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants(IRecursiveElementProcessor processor) in c:\Agent\work\e9a2fff71e84fb33\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 116
   at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants(IRecursiveElementProcessor processor) in c:\Agent\work\e9a2fff71e84fb33\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 116
   at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants(IRecursiveElementProcessor processor) in c:\Agent\work\e9a2fff71e84fb33\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 116
   at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants(IRecursiveElementProcessor processor) in c:\Agent\work\e9a2fff71e84fb33\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 116
   at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants(IRecursiveElementProcessor processor) in c:\Agent\work\e9a2fff71e84fb33\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 116
   at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants(IRecursiveElementProcessor processor) in c:\Agent\work\e9a2fff71e84fb33\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 116
   at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants(IRecursiveElementProcessor processor) in c:\Agent\work\e9a2fff71e84fb33\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 116
   at JetBrains.ReSharper.Daemon.CSharp.Stages.FileStructureCollectorProcess.ProcessFile(ICSharpFile file) in c:\Agent\work\e9a2fff71e84fb33\src\Daemon.CSharp\src\Stages\FileStructureCollectorStage.cs:line 286
   at JetBrains.ReSharper.Daemon.CSharp.Stages.CSharpDaemonStageProcessBase.Execute() in c:\Agent\work\e9a2fff71e84fb33\src\Daemon.CSharp\src\Stages\CSharpDaemonStageBase.cs:line 84
   at JetBrains.ReSharper.Daemon.Impl.DaemonProcessBase.DoHighlighting(DaemonProcessKind kind) in c:\Agent\work\e9a2fff71e84fb33\src\Daemon\src\Impl\DaemonProcessBase.cs:line 321
   --- End of inner exception stack trace ---
at JetBrains.ReSharper.Daemon.Impl.DaemonProcessBase.DoHighlighting(DaemonProcessKind) in c:\Agent\work\e9a2fff71e84fb33\src\Daemon\src\Impl\DaemonProcessBase.cs:line 329 column 19
at JetBrains.ReSharper.Daemon.Impl.VisibleDocumentDaemonProcess.DoHighlighting(Boolean) in c:\Agent\work\e9a2fff71e84fb33\src\Daemon\src\Impl\VisibleDocumentDaemonProcess.cs:line 188 column 9
at JetBrains.ReSharper.Daemon.Impl.<>c__DisplayClass1.<EnqueueHighlightingJob>b__0() in c:\Agent\work\e9a2fff71e84fb33\src\Daemon\src\Impl\VisibleDocumentDaemonProcess.cs:line 174 column 60
at JetBrains.ReSharper.Daemon.Impl.DaemonThread.ThreadProc() in c:\Agent\work\e9a2fff71e84fb33\src\Daemon\src\Impl\DaemonThread.cs:line 127 column 13
at System.Threading.ThreadHelper.ThreadStart_Context(Object)
at System.Threading.ExecutionContext.Run(ExecutionContext, ContextCallback, Object)
at System.Threading.ThreadHelper.ThreadStart()

14 comments

Hello Nick,

This is unfamous OutOfMemoryException, which most of the time caused by exhaustion
of virtual address space. Visual Studio is 32bit process, and it loads tonns
of DLLs, and it creates a lot of heaps and so on. All those modules fragments
address space to the point when CLR cannot allocate 16mb chunk of continuous
memory. At this point it fails. We could probably ignore and filter an error
(and you will have this option in upcoming ReSharper 4.5), but it means most
functions will not work as expected. At this point, you'd better restart
Visual Studio. On the other hand, if you have the case, when this problem
occures frequently or happens after certain operation, we would like to know.


Sincerely,
Ilya Ryzhenkov

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


0

Well I understand the error.

And thats all fine and dandy, but in the meantime you have quadrupled my development time because every character I type into my asp source view I have to wait 30 seconds for the error dialog to pop up click the igore execption of this type and click the ignore button.

it always sees that error as different from the last.

When I'm writing asp html I could really care less about what resharper is doing.

And honestly if I could wait 10 minutes to create a div with 5 web controls and no help from resharper until I decide to turn it back on.

I would take disable resharper anyday, since this causes me to spend hours after work on my web pages.

And rebooting isn't really a good option because I have 11 projects in my solution and it takes a long time to load.

Can't you just add a disable button and skip all exceptions?

It's extremely frustrating and even more to have you tell me I have to be a good boy and wait. Am I going to get a free coupon for Rogaine to replace all the hair i'm pulling out in the meantime?

All I have to say is I like resharper and its efforts, but a big "Ugg!" seems appropriate. I need a disable button!

Nick

0

Hi I don't have the memory issue but the editing of aspx/html side pages is horribly painful even on passible hardware (I have a Intel T9300-4GB-64bit system).  To avoid this I usually add the whole website project directory to the excuded folders list in RS options, but I would rather prefer a better way of filtering out files I don't want RS to analyse.  Like adding a file path and/or file pattern would be a huge help.  I understand that RS needs to analyse all the files to for it to work, but can't we switch off the RS UI stuff when editing the aspx/ascx side of things?  Maybe this would reduce the memory allocations?

0

Hi Nick,

I have a good solution to having RS disabled on VS startup and still be able to switch it on/off when I want.

To make some buttons that start and stop RS on the fly and prevent RS from automatically loading on VS startup, follow these instructions exactly:
  0. Make a full backup of your current settings from VS->Tools->Import and export...
  1. In the VS open up the "Macro IDE".
  2. Project -> Add existing item, select the macro file "ResharperUtil.vb".
  3. Close the "Macro IDE".

  4. In VS, right-click on any part of the menus, choose "Customise", change to "Commands".
  5. Select "Macros" in "Categories".
  6. Drag the two new macros onto an existing toolbar and set the images.
  7. Close VS completely - all instances.

  8. Go to your "My Documents\Visual Studio 2008\Settings" folder and make "CurrentSettings.vssettings" read-only.  This is a MUST!
  9. Open up VS, go to "Tools->Add-in manager" and untick all the checkboxes for "Resharper".
10. Close VS again.  VS will complain about not being able to write to its settings file (due to step 8) this is just a warning.  If VS was allowed to write to the settings file without RS started, then a ton of customisations will be lost.  The most important for me is the RS syntax highlighting colours getting nuked!  So you need to keep this read-only!

If you made it through all that pain, then now RS will not start on VS startup and you can use the two new buttons (macros) to start and stop RS at any time

Thanks to Alderan in the forums for posting the two brilliant VS macro functions to turn RS on and off on the fly:
   http://www.jetbrains.net/devnet/message/5218934#5218934

Maybe this helps - for me this is a killer setup as often I just need to make a 2-minute-noodle-code-fix to a fat website and don't need or want the full RS stuff slowing down the solution load up.

Edit: Forgot the files!



Attachment(s):
RS-off.bmp
RS-on.bmp
ResharperUtil.vb
0

Which version of ReSharper do you use?
Please try the latest nightly builds of ReSharper 4.5 - we've done tons of
memory/performance optimization issues

--
Eugene Pasynkov
ReSharper Technical Lead
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"


"resonantworks" <no_reply@jetbrains.com> wrote in message
news:18807987.4571232732794662.JavaMail.clearspace@app4.labs.intellij.net...

Hi I don't have the memory but the editing of aspx/html side pages is
horribly painful even on passible hardware (I have a Intel T9300-4GB-64bit
system). To avoid this I usually add the whole website project directory
to the excuded folders list in RS options, but I would rather prefer a
better way
of filtering out files I don't want RS to analyse. Like adding a file path
and/or file pattern would be a huge help. I understand that RS needs to
analyse all the files to for it to work, but can't we switch off the RS UI
stuff when editing the aspx/ascx side of things? Maybe this would reduce t
he memory allocations?

>

---
Original message URL:
http://www.jetbrains.net/devnet/message/5230740#5230740



0

I only see 4.1 and I know my boss would never allow me to use a beta version. Have we ever heard of emergency patches when customers need it extremely bad? This has been known for 6+ months.

You need to send a patch out to developers who are having to cry at work all day when thier boss says "Why did you miss your deadline?" ..."Resharper is sucking the big one right now.." boss: "Why didn't you just uninstall the dame thing?" I say "because I still need it on the other 12 projects in my solution" I say "Fine, I'll uninstall it tomorrow so I can sleep the rest of the week."

Whether jet brains cares or not this is a serious issue and should be a hot fix. Not forcing me to wait months for this. My first support ticket was back in June and you claim it's still in beta. You must be trying to be like Microsoft.

I love you Resharper but, geez get a grip.

I can't rewrite my project files because many developers are using them and I would be kicked out of the door for hacking a projects that the lifeblood of the company.

I wake up in cold sweats at night when I get assigned web changes.

click a letter , wait 15 seconds,click ignore,click a letter, wait 15 seconds ,click ignore,click a letter ,wait 15 seconds, click ignore,click a letter , wait 15 seconds,click ignore,click a letter,  wait 15 seconds,click ignore,click a letter , wait 15 seconds,click ignore,click a letter , wait 15 seconds,click ignore,click a letter,  wait 15 seconds,click ignore,click a letter , wait 15 seconds,click ignore



is the step involved to write <asp:button runat="server" />

During the wait time I am crying on the inside in my cubicle.

elapsed time is 10 minutes......

We need a hotfix!!1!!!1!!!!!!

I apologize for my frustration but...I get extremely upset when I have make web changes to div's that take all of 5 seconds to make and it takes 30+ minutes. I have to restrat my solution many times and loading it takes 5+ minutes. ugggg

People who have beast application are suffering bad.

0

Hello Nick,

If it were that easy to lower memory consumption, we would have done it long
ago. It is not like quick patch, or something we don't care about. We would
like to make ReSharper use no memory at all, but unfortunately we don't know
how to do this. Processing ASP files takes a lot of resources and memory,
and we don't have any idea to lower it right away. Without processed files
there is no reason to keep ReSharper running, it would just show false errors,
warnings, fail on refactorings and such.

So, if you have such huge website and can't do anything to reduce its size,
your best bet would be to disable ReSharper before opening it. You can do
it in Tools/Add-in manager, just uncheck the mark near ReSharper before loading
website into Visual Studio.

Note, that disabling display of OutOfMemoryException will not help, because
process is low at memory and other failures will happen all the time, and
GC will kick in every other second to try free some memory and all will be
slow and failing.

As already said, we are working on this in 4.5 by doing HUGE changes in architecture,
source code processing algorithms and so on. While this change will definitly
improve performance and lower memory consumptions on many web sites, there
always will be projects that can be handled by VS and cannot be handled when
ReSharper is added. This is quite unavoidable, if you think about it. Unfortunately,
your website cannot be handled by ReSharper 4.1. It may fit or not fit into
ReSharper 4.5, depending on the size.

Sincerely,
Ilya Ryzhenkov

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


NT> I only see 4.1 and I know my boss would never allow me to use a beta
NT> version. Have we ever heard of emergency pacthes when customers need
NT> it extremely bad? This has been known for 6+ months.
NT>
NT> You need to send a patch out to developers who are having to cry at
NT> work all day when thier boss says "Why did you miss your deadline?"
NT> ..."Resharper is sucking the big one right now.." boss: "Why didn't
NT> you just uninstall the dame thing?" I say "because I still need it
NT> on the other 12 projects in m
NT>
NT> y solution" I say "Fine, I'll uninstall it tomorrow so I can sleep
NT> the rest of the week."
NT>
NT> Whether jet brains cares or not this is a serious issue and should
NT> be a hot fix. Not forcing me to wait months for this. My first
NT> support ticket was back in June and you claim it's still in beta.
NT> You must be trying to be like Microsoft.
NT>
NT> I love you Resharper but, geez get a grip.
NT>
NT> I can't rewrite my project files because many developers are using
NT> them and I would be kicked out of the door for hacking a projects
NT> that the lifeblood of the company.
NT>
NT> I wake up in cold sweats at night when I get assigned web changes.
NT>
NT> click a letter , wait 15 seconds,click ignore,click a letter, wait
NT> 15 seconds ,click ignore,click a letter ,wait 15 seconds, click
NT> ignore,click a letter , wait 15 seconds,click ignore,click a letter,
NT> wait 15 seconds,click ignore,click a letter , wait 15 seconds,click
NT> ignore,click a letter , wait 15
NT> seconds,click ignore,click a letter, wait 15 seconds,click
NT> ignore,click a letter , wait 15 seconds,click ignore
NT> is the step involved to write <asp:button runat="server" />
NT>
NT> During the wait time I am crying on the inside in my cubicle.
NT>
NT> elapsed time is 10 minutes......
NT>
NT> We need a hotfix!!1!!!1!!!!!!
NT>
NT> I apologize for my frustration but...I get extremely upset when I
NT> have make web changes to div's that take all of 5 seconds to make
NT> and it takes 30+ minutes. I have to restrat my solution many times
NT> and loading it takes 5+ minutes. ugggg
NT>
NT> People who have beast application are suffering bad.
NT>
NT> ---
NT> Original message URL:
NT> http://www.jetbrains.net/devnet/message/5230770#5230770


0

Hi Nick,

If you have a solution with a website project and a few class libraries then this is what I do in when the website part is too big for RS:
    1. Open the offending solution in visual studio.
    2. Determine the path of the website project.
    3. VS -> ReSharper -> Options.
    4. Code Inspection -> Settings -> Advanced...
    5. Add Folder, choose the path found in step (2).

Now you will have the full RS goodness on all your other projects, but not on your website project.

On a side note, static code analysis is inherently complex, memory and processor intensive.  I seriously doubt there would ever be a 'quickfix' for any product like RS to solve those issues overnight.  It takes a huge amount of brilliant ideas to get such a system to be optimised for both memory and processor usage simultaneously while still being an 'acceptable' solution.

0

I'm using RS 4.5.1153.0.  I wish I had the time to keep up to date with the nightlies, but that one seems mostly stable for me for now.   And yes I have noticed a huge speed diff between 4.1 and 4.5

0

well I understand that its extremely complex and I didn't expect a quick fix overnight...This issue has been in existence since at least June and I would expect at least a friendly notification that my bug is being addressed, rather than telling me i'm just screwed from support and never having an after thought.

Your idea is perfect though. It will allow me to wait for the next version.

I'm off my soapbox now....

Thanks
,Nick

0

I don't know if they told you that you were screwed or not, they are telling you the facts and letting you know the situation that they are in.  Fact is, if you would have taken a few moments to search the forums you would have seen the 1000 other posts talking towards this.  Everybody knows that major changes are on the way and we are all patiently waiting for the 4.5 release.

0

Fact is, if you would have taken a few moments to search the forums you would have seen the 1000 other posts talking towards this.

The fact is I was stating to Jet Brains I was sick of this after seeing it for 8+ months. I was not asking for a response. Why you stated this I have no idea. Trolling is a sickness that needs professional help. And this topic has been over for a while and I don't see the point of your reply.

Everybody knows that major changes are on the way and we are all patiently waiting for the 4.5 release.

Yes I am aware of that. I have been patiently waiting since March.

Thanks for your response.

0

Yeah I can't wait for it to go live. Here we're not allowed to use anything beta. I'm almost over the bend.

0

You are welcome, just pointing out that you were being overly harsh given the situation.

0

Please sign in to leave a comment.