- Home /
- Visual Studio /
This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn more
Report an issue
in Visual Studio Installer or Visual Studio
This allows diagnostic information about the program to be included in your report
1. Installer or Visual Studio
2. Report a Problem
3. Type and Submit
Available on Visual Studio 2017, Installer, and newer releases
Would you like to know more?
VS2017 (15.3) OutOfMemoryException (in SQLite)
After updating VS2017 from 15.2 to 15.3, it crashes every time when I do this:
- open one of my solutions (120 C# projects) - checked standard and lightweight solution load, both cases cause a crash
- click on the name of one of the methods
- (VS starts eating memory and CPU and becomes unresponsive)
- wait a few minutes
- VS crashes
This is 100% reproducible.
The Event Log entry is as follows:
Application: devenv.exe Framework Version: v4.0.30319Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
at System.Windows.Media.Composition.DUCE+Channel.SyncFlush()
at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean, System.Nullable`1<ChannelSet>)
at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr)
at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)
at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
I've captured memory usage screenshots:
- The 1st one is after just starting VS without a solution.
- The 2nd one is after opening the solution and not doing anything else.
- The 3rd one is directly after clicking the method name (step #2 above); the increase from using ~700MB to ~3.3GB RAM happens in a split second. It then sits like this (RAM usage doesn't change much and CPU is ~12-13% which is one full core on my 8-core machine) for a few minutes and then crashes.
The screenshots I attached using the problem reporting tool are not visible... You might want to fix that.
In the meantime, here they are:
1.
2.
And screenshot #3, because apparently I can't add 3 images to a comment :-/
3.
I also reported a possibly related OOM crash in RoslynCodeAnalysisService32.exe here: https://github.com/dotnet/roslyn/issues/21580.
It looks like you have a couple of things going on here. Your picture at #2 implies that ServiceHub.RoslynCodeAnalysis is running very low on memory. The picture at #3 says devenv.exe is going to run out of memory.
I'd like to look at those two issues separately.
Here are some instructions to capture a memory trace:
1. Download and extract PerfView.exe. http://www.microsoft.com/en-us/download/details.aspx?id=28567
2. Run PerfView.exe collect /circularmb=10000 /gconly /zip:true /nogui /AcceptEULA from an elevated command prompt. This will launch another window and begin tracing.You will need about 10GB free on the drive you're running this on.
3. Reproduce the scenario - for example set up your machine with the solution open in VS, then do step 1&2, and then when it starts tracing, click the method name to reproduce your second problem. Once it finishes allocating memory (and presumably crashes) you can stop the trace.
4. Stop the trace by pressing S in the console window that shows up from step 2. This will generate a PerfViewData.Etl.Zip file in the current directory. Use a different subdirectory for each trace. Upload this as an attachment for a comment on this thread.
Repeat the whole process for the solution load so I can dig into the 3.2GB allocation in Roslyn. This will probably be what the Roslyn guys need to analyze your OOM bug you filed for them on github. You can either give the trace to them there, or upload it here and I'll point them to it.
Thanks!
Adrian, thanks for the reply.
I'm attaching two traces:
- PerfViewGCOnly-solution-load.etl.zip
Collected while I started VS and opened the solution. Just after I stopped collection, some of VS' external processes crashed and VS showed the yellow information bar about this (two of them, actually). Not sure how helpful this is. - PerfViewGCOnly-crash.etl.zip
I tried to reproduce the scenario with the crash, but was unable to at first. I thought that it may be due to some obscure reason such as the list of files I have open in that solution - I closed some of then recently, so I reopened a few, most notably the one with the method which causes the crash. And now it's even worse than before - VS crashes all by itself without me doing anything after the solution loads. This trace captures this scenario (from starting VS, though opening the solution, perfviewgconly-solution-loadetl.zipperfviewgconly-crashetl.zipuntil it crashes and VS exits).
It's exactly the same problem with our team!!! (30 cs project, some of csproj has more than 15,000 cs file)
I've noticed something similar here. However, the stack trace is slightly different. I've worked around this by uninstalling VS2017 version 15.3 and reinstalling VS2017 version 15.0.
Could you paste the stack trace here?
Truncated
Application: devenv.exeFramework Version: v4.0.30319Description: The application requested process termination through System.Environment.FailFast(string message).Message: System.Threading.Tasks.TaskSchedulerException: An exception was thrown by a TaskScheduler. ---> System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. at System.Threading.Thread.StartInternal(IPrincipal principal, StackCrawlMark& stackMark) at System.Threading.Thread.Start(StackCrawlMark& stackMark) at System.Threading.Thread.Start(Object parameter) at System.Threading.Tasks.ThreadPoolTaskScheduler.QueueTask(Task task) at System.Threading.Tasks.Task.ScheduleAndStart(Boolean needsProtection) --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ScheduleAndStart(Boolean needsProtection) at System.Threading.Tasks.Task.InternalStartNew(Task creatingTask, Delegate action, Object state, CancellationToken cancellationToken, TaskScheduler scheduler, TaskCreationOptions options, InternalTaskOptions internalOptions, StackCrawlMark& stackMark) at System.Threading.Tasks.TaskFactory.StartNew(Action`1 action, Object state, CancellationToken cancellationToken, TaskCreationOptions creationOptions, TaskScheduler scheduler) at Roslyn.Utilities.ObjectWriter.WriteObject(Object instance, IObjectWritable instanceAsWritableOpt) at Microsoft.CodeAnalysis.CSharp.Syntax.InternalSyntax.IdentifierNameSyntax.WriteTo(ObjectWriter writer) at Microsoft.CodeAnalysis.GreenNode.Roslyn.Utilities.IObjectWritable.WriteTo(ObjectWriter writer) at Roslyn.Utilities.ObjectWriter.WriteObjectWorker(IObjectWritable writable) at Roslyn.Utilities.ObjectWriter.WriteObject(Object instance, IObjectWritable instanceAsWritableOpt) at Microsoft.CodeAnalysis.CSharp.Syntax.InternalSyntax.MemberAccessExpressionSyntax.WriteTo(ObjectWriter writer) at Microsoft.CodeAnalysis.GreenNode.Roslyn.Utilities.IObjectWritable.WriteTo(ObjectWriter writer) at Roslyn.Utilities.ObjectWriter.WriteObjectWorker(IObjectWritable writable) at Roslyn.Utilities.ObjectWriter.WriteObject(Object instance, IObjectWritable instanceAsWritableOpt) at Microsoft.CodeAnalysis.CSharp.Syntax.InternalSyntax.InvocationExpressionSyntax.WriteTo(ObjectWriter writer) at Microsoft.CodeAnalysis.GreenNode.Roslyn.Utilities.IObjectWritable.WriteTo(ObjectWriter writer) at Roslyn.Utilities.ObjectWriter.WriteObjectWorker(IObjectWritable writable) at Roslyn.Utilities.ObjectWriter.WriteObject(Object instance, IObjectWritable instanceAsWritableOpt) at Microsoft.CodeAnalysis.CSharp.Syntax.InternalSyntax.InvocationExpressionSyntax.WriteTo(ObjectWriter writer) at Microsoft.CodeAnalysis.GreenNode.Roslyn.Utilities.IObjectWritable.WriteTo(ObjectWriter writer) at Roslyn.Utilities.ObjectWriter.WriteObjectWorker(IObjectWritable writable) at Roslyn.Utilities.ObjectWriter.WriteObject(Object instance, IObjectWritable instanceAsWritableOpt) at Microsoft.CodeAnalysis.CSharp.Syntax.InternalSyntax.ArgumentSyntax.WriteTo(ObjectWriter writer) at Microsoft.CodeAnalysis.GreenNode.Roslyn.Utilities.IObjectWritable.WriteTo(ObjectWriter writer) at Roslyn.Utilities.ObjectWriter.WriteObjectWorker(IObjectWritable writable) at Roslyn.Utilities.ObjectWriter.WriteObject(Object instance, IObjectWritable instanceAsWritableOpt) at Microsoft.CodeAnalysis.CSharp.Syntax.InternalSyntax.ArgumentListSyntax.WriteTo(ObjectWriter writer) at Microsoft.CodeAnalysis.GreenNode.Roslyn.Utilities.IObjectWritable.WriteTo(ObjectWriter writer) at Roslyn.Utilities.ObjectWriter.WriteObjectWorker(IObjectWritable writable) at Roslyn.Utilities.ObjectWriter.WriteObject(Object instance, IObjectWritable instanceAsWritableOpt) at Microsoft.CodeAnalysis.CSharp.Syntax.InternalSyntax.CompilationUnitSyntax.WriteTo(ObjectWriter writer) at Microsoft.CodeAnalysis.GreenNode.Roslyn.Utilities.IObjectWritable.WriteTo(ObjectWriter writer) at Roslyn.Utilities.ObjectWriter.WriteObjectWorker(IObjectWritable writable) at Roslyn.Utilities.ObjectWriter.WriteObject(Object instance, IObjectWritable instanceAsWritableOpt) at Microsoft.CodeAnalysis.SyntaxNode.SerializeTo(Stream stream, CancellationToken cancellationToken) at Microsoft.CodeAnalysis.Host.AbstractSyntaxTreeFactoryService.RecoverableSyntaxRoot`1.d__6.MoveNext()Stack: at System.Environment.FailFast(System.String, System.Exception) at Microsoft.CodeAnalysis.FailFast.OnFatalException(System.Exception) at Microsoft.CodeAnalysis.ErrorReporting.FatalError.Report(System.Exception, System.Action`1) at Microsoft.CodeAnalysis.ErrorReporting.FatalError.Report(System.Exception) at Roslyn.Utilities.TaskExtensions.ReportFatalErrorWorker(System.Threading.Tasks.Task, System.Object) at System.Threading.Tasks.ContinuationTaskFromTask.InnerInvoke() at System.Threading.Tasks.Task.Execute() at System.Threading.Tasks.Task.ExecutionContextCallback(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef) at System.Threading.Tasks.Task.ExecuteEntry(Boolean) at System.Threading.Tasks.ThreadPoolTaskScheduler.TryExecuteTaskInline(System.Threading.Tasks.Task, Boolean) at System.Threading.Tasks.TaskScheduler.TryRunInline(System.Threading.Tasks.Task, Boolean) at System.Threading.Tasks.TaskContinuation.InlineIfPossibleOrElseQueue(System.Threading.Tasks.Task, Boolean) at System.Threading.Tasks.StandardTaskContinuation.Run(System.Threading.Tasks.Task, Boolean) at System.Threading.Tasks.Task.FinishContinuations() at System.Threading.Tasks.Task.FinishStageThree() at System.Threading.Tasks.Task.FinishStageTwo() at System.Threading.Tasks.Task.Finish(Boolean) at System.Threading.Tasks.Task`1[[System.Threading.Tasks.TaskExtensions+VoidResult, System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].TrySetException(System.Object) at System.Threading.Tasks.UnwrapPromise`1[[System.Threading.Tasks.TaskExtensions+VoidResult, System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].TrySetFromTask(System.Threading.Tasks.Task, Boolean) at System.Threading.Tasks.UnwrapPromise`1[[System.Threading.Tasks.TaskExtensions+VoidResult, System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ProcessInnerTask(System.Threading.Tasks.Task) at System.Threading.Tasks.UnwrapPromise`1[[System.Threading.Tasks.TaskExtensions+VoidResult, System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ProcessCompletedOuterTask(System.Threading.Tasks.Task) at System.Threading.Tasks.UnwrapPromise`1[[System.Threading.Tasks.TaskExtensions+VoidResult, System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InvokeCore(System.Threading.Tasks.Task) at System.Threading.Tasks.UnwrapPromise`1[[System.Threading.Tasks.TaskExtensions+VoidResult, System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Invoke(System.Threading.Tasks.Task) at System.Threading.Tasks.Task.FinishContinuations() at System.Threading.Tasks.Task.FinishStageThree() at System.Threading.Tasks.Task.FinishStageTwo() at System.Threading.Tasks.Task.Finish(Boolean) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef) at System.Threading.Tasks.Task.ExecuteEntry(Boolean) at System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
Hey Jakub, can you supply us with a repro solution where we can investigate this? That would be very helpful.
Alternatively, if you could provide us with a link to the roslyn db cache file that would be helpful. The cache file will be under your solution directory in a folder called: .vs\Roslyn\v15\sqlite3\storage.ide. Thanks!
I can't share the solution (it's company property), but I can share the Roslyn cache. How can I do so privately, is there any place I can upload this? Do you need the cache from just after a crash, before a crash or it doesn't matter?
I reported a similar issue to the folks at DevExpress, since I thought CodeRush for Roslyn was at fault (and tbh, I'm not exactly sure whether it is completely innocent), but I noticed that disabling CRR made a difference (obviously, since its Roslyn-based analyzers don't run) and also that disabling Code Lens made a difference (instead of memory going up and levelling, it went up briefly and then went down again).
But disabling either is something I'd rather not do, for the convinience it brings.
Obviously, this is on VS 2017 Enterprise (15.3.2), since other editions don't have Code Lens. Not sure if thats the case for Jakub.
It's VS 2017 Enterprise here as well (all versions from 15.3 to the current 15.3.2) - no Roslyn-related extensions other than what's bundled with VS though.
Can you check if disabling Code Lens makes a difference for you?
We have the same problem!!
https://github.com/dotnet/roslyn/issues/21730
https://github.com/dotnet/roslyn/issues/21650
It surprises me there are so few upvotes on this issue. Let's show MS folks this is important!
Same problem here with a large project (but it has nothing to do with SQLite). We can't use Visual Studio since one month, so, where can we download version 15.2 that worked well ?
Best Solution
Thank you, I confirm 15.4.1 fixes the issue for me! :-)
Nope, no change there. On the very 1st Go To Implementation, everything locks up and VS crashes after a few seconds maximizing to 3.5 GB RAM usage.
We downgraded to 15.2 for now.
There is still a problem when proceeding as follows.
https://github.com/dotnet/roslyn/wiki/Performance-considerations-for-large-solutions
- Disabling Full Solution Diagnostics
- Disabling CodeLens
- Disabling Solution Crawler
- Adjusting File Caching Threshold(RecoverableTreeLengthThreshold = 1)
- Disabling Reference Promotion
- Specifying a main method explicitly
- Checked Option-Text Editor-C#-Advanced-Perform editor feature analysis in external process
I strongly recommend using Rider(https://www.jetbrains.com/rider/)
167 People are following this
