OutOfMemberyError in lexing file : RSRP-18766

Back to Search

Project	ReSharper
Priority	Show-stopper
Type	Performance Problem
Fix versions	Mirabile Futurum
State	Open
Assignee	Evgeny Pasynkov
Subsystem	No subsystem
Affected versions	No Affected versions
Fixed in build	No Fixed in build

Created by Valentin Kipiatkov
5 years ago (06 Aug 2006 01:05)
Updated by Sergey Shkredov
3 weeks ago (05 May 2012 15:30)
Jira: RSRP-18766
(history, comments)

RSRP-18766 OutOfMemberyError in lexing file

Issue is visible to: All Users

Links — Show as list

No description

Ben Robbins

08 Aug 2006 21:48

5 years ago

Re: #18766- OutOfMemberyError in lexing file
It's pretty easy to get this to occur. You want a largish solution (our is 37 projects), with some very large files (we have about 10 files that are > 10k LOC).

You then run the application through the debugger. The next time you try and build the app you will probably run out of memory. You can just edit and work away and it will eventually happen, but I've found that using the "build and debug" button (the one that looks like a play icon in the toolbar) you can reliably get this assertion the next time you build.

This is quite reproducable (as can be seen by all the duplicates) and has been around for ages. I can't understand why JetBrains haven't fixed this :(

Boris Nikolaevich

25 Oct 2006 20:42

5 years ago

A large solution is not required to produce. We have one web project and about 5 supporting class libraries in the solution. However, it does seem that the error is most likely to occur when there are dependent project references: Web project references ClassLibraryA and ClassLibraryB; ClassLibraryA references ClassLibraryB; ClassLibraryB references ClassLibraryC and ClassLibraryD.

We have uninstalled the trial of Resharper because the error occurred too frequently.

Torkil Olsen

14 Nov 2006 02:52

5 years ago

I have the same problem. Is there any log file you want to better debug this issu?

Torkil Olsen

06 Dec 2006 12:13

5 years ago

Hi

Anything new info on when this will be resolved?

Torkil Olsen

23 Jan 2007 11:47

5 years ago

Why is this marked as Fixed in version 2.0.4?

The errors are present in every version of 2.5.*

Edward Wilde

12 Mar 2007 20:40

5 years ago

Like the previous commentor, why has this issue been marked as fixed? I can confirm it's still reproducable in the current release (2.5 build 326).

I get this error frequently, and i'm stating to think that I might stop using resharper as this is grinding my VS to a halt about twice a day.

Hope this gets fixed soon. :)

Robbie Coleman

26 Mar 2007 20:59

5 years ago

(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)
h1. JetBrains, this is your 7 ^1/2^ Month Wake-up Call
(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)(*r)(!)

_YES_ this _is_ still happening, and _*YES*_ enough people _do_ care about it!

Please at least respond in this thread so we know you _are_ listening. ;)

Thanks,
Robbie Coleman

Evgeny Pasynkov

26 Mar 2007 22:17

5 years ago

We're still tracking this issue, but haven't yet found a way to fix it :(

Robbie Coleman

26 Mar 2007 23:23

5 years ago

It _is_ great to here from you Eugene! Thanks for re-opening this bug and replying to the thread as well.

Sorry about the extreme volume level of my previous comment, but sometimes noise works.

;)

Gunnlaugur Thor Briem

27 Mar 2007 14:49

5 years ago

And the award for creative use of a Jira comment field goes to ... :)

It's OK Eugene, we still like you guys. We just needed to know that this was getting the priority it deserves.

Sebastian Good

17 May 2007 21:14

5 years ago

we must shut down our resharper 2-3 times per day at a cost of many minutes of lost time. this bug is extremely frustrating to all of us! it has to be a memory leak

Sarah Fernandezlopez

17 May 2007 21:23

5 years ago

There are certain files that cause this to happen more often than others. Since I work with those files on my project I hit this 5-6 times a day. I finally uninstalled resharper. Then missed it so bad and reinstalled it. Now I just keep open task manager while I work and shut VS down when the memory consumption gets too high. Seems a tad bit ridiculous.

Sarah Fernandezlopez

17 May 2007 21:29

5 years ago

Is there - or could there be - a way to tell Resharper not to look at certain files. This would at least mitigate the issue. We have a few key files that we know resharper will die on if we keep them open. If we could tell resharper not to scan those files, we'd hit this a LOT less often.

Vladimir Reshetnikov

17 Jun 2007 13:19

4 years ago

Typo: OutOfMembery -> OutOfMemory.

Robbie Coleman

17 Jul 2007 01:45

4 years ago

Y'ALL are quickly approaching the ONE YEAR mark on this exception!!!!

Please tell me a fix or AT LEAST workaround is NOW in sight.

This thing raised it's ugly head back in August of 2006 in version 2.0.x and carried over into 2.5.x. That does not sound tooo bad, BUT FOR IT TO BE CARRIED INTO THE NEXT MAJOR VERSION 3.0.x!!!????!!!???

Frustration with crashed sessions is getting to be quite annoying.

Evgeny Pasynkov

17 Jul 2007 12:49

4 years ago

This issue has nothing with a memory insufficiency.
Currently, we do not know why this occurs, but we are working to resolve this problem

Kristian Kjær

25 Jul 2007 10:25

4 years ago

I get this error when I open a large (C#) file (~1500 lines). I have other files of that size, too, but these give me no problems. The error occurs, when ReSharper performs the code analysis, so I get around the problem by turning of code analysis for that specticular file (Ctrl+8). Then I can't use ReSharpers nice features for that file, but it works everywhere else.

The symptoms for the error in my case is that when I open the particular file, the devenv.exe process consumes 100% of my CPU and the memory consumption rises endlessly until the error occur.

Just a hint for a workaround, if your symptoms are simular :)

Valentin Kipiatkov

25 Jul 2007 16:13

4 years ago

Kristian,

Could you please send us this file? You can send it me directly to

valentin at jetbrains.com

Magnus Werner

13 Sep 2007 10:25

4 years ago

This happens to me quite frequently with large files. Our test department likes to stick all test cases for a project in the same file so they get LARGE! A suggestion, until it is fixed, it would be nice if you could introduce a "black list" for files that this error occurs in i.e. when the OutOfMemory exception thrown while lexing a file, ReSharper would put that file on the list and not try to do its magic on it anymore. This way we would be able work with ReSharper on the rest of the files without hitting the wall every now and then.

Jeffrey T. Fritz

26 Oct 2007 06:38

4 years ago

I am working on a VS2005 project with v3.0.2 and I received this error daily. Our solution has 37 sub-projects and I have stripped down my build configuration to compile the topmost 12 that I am working with daily. We have more than 1,000KLOC in our entire solution

My devenv.exe memory footprint swells from 128MB at the beginning of the day to 950MB over 8 hours of work. If I attempt to build once I have crossed the 900MB mark, I receive this error repeatedly.

I do not experience this scenario when Resharper is not running.

I have recently upgraded my workstation from 2GB of RAM to 4GB of RAM to compensate for this problem, as I truly believe in Resharper as a fantastic tool to assist me as a developer, however... I am only writing more code, and this kind of behavior on the part of the tool may force me to ditch the tool altogether in order to remain productive.

Please contact me if you need more assistance in tracking down this issue.

DeeJay Bettes

30 Nov 2007 20:45

4 years ago

We only seem to have this issue when some developers are using the System TEMP folder for caching and others use the project folder. Just thought I'd mention what we've found to aide in the search for a solution.

Lutz Jacob

07 Jan 2008 15:48

4 years ago

We have the same Exeption in our own application with a very similar call stack. I think it is a bug in the .NET Framework itself.

System.OutOfMemoryException: Eine Ausnahme vom Typ System.OutOfMemoryException wurde ausgelöst.

…

System.OutOfMemoryException: Eine Ausnahme vom Typ System.OutOfMemoryException wurde ausgelöst.
 bei System.Collections.Generic.ObjectEqualityComparer`1.Equals(T x, T y)
 bei System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
 bei System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value)

Jason Monroe

18 Jan 2008 00:21

4 years ago

Just recieved this error today..

Environment:
Resharper 3.1
VS 2005 Team Suite SP1

Workstation:
Duel Xeon (Duel Core) 2.6ghz
8GB Ram
Windows XP x64

As a side note, the 3.1 installer failes to recognize VS2005 as having SP1 installed on XP x64...

Craig Fisher

25 Apr 2008 20:56

4 years ago

No word on a fix for this? Coming up to two years old and its still costing us time daily!

Jeffrey T. Fritz

25 Apr 2008 21:38

4 years ago

Honestly, this one is killing me...

I had recommended that my company pick up Resharper licenses for our whole team, but everybody is getting this one in a bad way on a very regular basis (each user hits this several times daily) with the trial version of 3.1

My team has since uninstalled the trial and are awaiting word on a fix before purchasing R# 4.0

Josh Rogers

06 Jun 2008 02:52

3 years ago

This error is beginning to get costly for my company, I am constantly having to restart VS to clear this error, and with 2 gig of ram I should not be getting out of memory issues. I am a relatively new customer and had I experienced this issue as many times as I do now during the trial I might have thought twice about suggesting my company purchase this product. I can't imagine a development team moving forward so vigorously on version 4 when you have such a glaring bug as this causing issues and being open for such a long period of time. Please JetBrains do something about this!

Alan Graham

10 Jun 2008 14:02

3 years ago

This is now affecting me again badly in Resharper 4.0 RC/Beta and I will be recommending we don't upgrade until it's fixed

Alan Graham

24 Jul 2008 13:21

3 years ago

Visual Studio is now using 900MB ram, compared to colleague with identical machine but no ReSharper who is using 200MB. I have had around 20 different crashes in the past week and am now looking to uninstall 3.1. Are Jet Brains addressing this issue which is now almost 2 years old?

Lee Richardson

12 Jan 2009 21:47

3 years ago

This bug is still occurring in 2009, making it 2 1/2 years old?! JetBrains and/or Eugene Pasynkov is there any update on this? Please help, this is very frustrating.

Eugene Petrenko

16 Mar 2009 21:26

3 years ago

See http://jetbrains.net/tracker/issue/TW-7361

TeamCity plugin version 4.0.31.0
VS
9.0.0.0
Plugin
ServerVersion: 4.0.0.10|4.0.2|8222
Server
ServerVersion: 4.0.0.10|4.0.2|8222

Message:Failed to create the component "JetBrains.ProjectModel.Impl.ExternalChangeProcessor, JetBrains.Platform.TeamCity.ProjectModel, Version
4.0.31.0, Culture
neutral, PublicKeyToken
1010a0d8d6380325". Exception has been thrown by the target of an invocation. Exception has been thrown by the target of an invocation.
Description:
JetBrains TeamCity 4.0 plugin for Microsoft(R) Visual Studio(TM) Version
4.0.31.0, Edition
, Built
2009-01-28T13:23:10, Configuration
Netfx20, VsVersion
9.0
Exception:
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stacktrace:

 at System.Drawing.SafeNativeMethods.Gdip.GdipLoadImageFromStream(IStream stream, IntPtr& image)

…

 at System.Drawing.SafeNativeMethods.Gdip.GdipLoadImageFromStream(IStream stream, IntPtr& image)
 at System.Drawing.Image.FromStream(Stream stream, Boolean useEmbeddedColorManagement, Boolean validateImageData)
 at System.Drawing.Image.FromStream(Stream stream)
 at JetBrains.ProjectModel.Impl.ExternalChangeProcessor.MyStatusBarIndicator..ctor() in c:\Agent\work\b5eba76a2daba6e4\Platform\src\ProjectModel\src\impl\ExternalChangeProcessor.cs:line 123
 at JetBrains.ProjectModel.Impl.ExternalChangeProcessor..ctor(ISolution solution) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\ProjectModel\src\impl\ExternalChangeProcessor.cs:line 27

Exception has been thrown by the target of an invocation.
Stacktrace:

 at System.RuntimeMethodHandle._InvokeConstructor(Object[] args, SignatureStruct& signature, IntPtr declaringType)

…

 at System.RuntimeMethodHandle._InvokeConstructor(Object[] args, SignatureStruct& signature, IntPtr declaringType)
 at System.RuntimeMethodHandle.InvokeConstructor(Object[] args, SignatureStruct signature, RuntimeTypeHandle declaringType)
 at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
 at JetBrains.ComponentModel.ComponentContainer.ComponentDeclarationCreate(ComponentDescriptor declaration) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\Shell\src\ComponentModel\ComponentContainer.cs:line 226

Failed to create the component "JetBrains.ProjectModel.Impl.ExternalChangeProcessor, JetBrains.Platform.TeamCity.ProjectModel, Version
4.0.31.0, Culture
neutral, PublicKeyToken
1010a0d8d6380325". Exception has been thrown by the target of an invocation. Exception has been thrown by the target of an invocation.
Stacktrace:

 at JetBrains.ComponentModel.ComponentContainer.ComponentDeclarationCreate(ComponentDescriptor declaration) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\Shell\src\ComponentModel\ComponentContainer.cs:line 240

…

 at JetBrains.ComponentModel.ComponentContainer.ComponentDeclarationCreate(ComponentDescriptor declaration) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\Shell\src\ComponentModel\ComponentContainer.cs:line 240
 at JetBrains.ComponentModel.ComponentContainer.JetBrains.ComponentModel.ICollectionChangedEventSink.OnAdd(ICollection`1 items) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\Shell\src\ComponentModel\ComponentContainer.cs:line 361
 at JetBrains.ComponentModel.ComponentDeclarationsCache.AdviseComponentDeclarationsCollectionChange(ICollectionChangedEventSink`1 sink) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\Shell\src\ComponentModel\ComponentDeclarationsCache.cs:line 48
 at JetBrains.ComponentModel.ComponentContainer.InitializeComponents(ComponentDeclarationsCache declarationscache) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\Shell\src\ComponentModel\ComponentContainer.cs:line 122
 at JetBrains.ComponentModel.XmlExternalizableComponentContainer.InitializeComponents(ComponentDeclarationsCache declarationscache) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\Shell\src\ComponentModel\XmlExternalizableComponentContainer.cs:line 380
 at JetBrains.ProjectModel.Impl.SolutionBase.InitializeComponents() in c:\Agent\work\b5eba76a2daba6e4\Platform\src\ProjectModel\src\impl\SolutionBase.cs:line 35
 at JetBrains.ProjectModel.Impl.ProjectFactoryImpl.CreateSolution(FileSystemPath solutionFilePath) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\ProjectModel\src\impl\ProjectFactoryImpl.cs:line 92
 at JetBrains.VSIntegration.ProjectModel.VSSolutionManager.ProcessSolution(String solutionFile) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\VSIntegration\src\ProjectModel\VSSolutionManager.cs:line 494
 at JetBrains.VSIntegration.ProjectModel.VSSolutionManager.OpenVSSolution(Boolean afterOpenSolution) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\VSIntegration\src\ProjectModel\VSSolutionManager.cs:line 403
 at JetBrains.VSIntegration.ProjectModel.VSSolutionManager.<>c__DisplayClass4.b__3() in c:\Agent\work\b5eba76a2daba6e4\Platform\src\VSIntegration\src\ProjectModel\VSSolutionManager.cs:line 359
 at JetBrains.Threading.ReentrancyGuard.Execute(String name, Action action) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\Util\src\Concurrency\ReentrancyGuard.cs:line 303
 at JetBrains.Threading.ReentrancyGuard.ExecuteOrQueue(String name, Action action) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\Util\src\Concurrency\ReentrancyGuard.cs:line 336
 at JetBrains.Threading.Invocator.ExecuteOrQueue(String name, Action action) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\Shell\src\Threading\Invocator.cs:line 125
 at JetBrains.VSIntegration.ProjectModel.VSSolutionManager.QueueAction(Action action) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\VSIntegration\src\ProjectModel\VSSolutionManager.cs:line 309
 at JetBrains.VSIntegration.ProjectModel.VSSolutionManager.OnAfterOpenSolution(Object pUnkReserved, Int32 fNewSolution) in c:\Agent\work\b5eba76a2daba6e4\Platform\src\VSIntegration\src\ProjectModel\VSSolutionManager.cs:line 356