When fiddling around OOM exception happens #300
Labels
Milestone
Comments
|
Here the some information for start as you see there some strange data - 2 listing all that objects I found that only one of that object is take that space. other is 124 bytes in size. Now output of offending object which probably indicates that 191MB was just allocating before I receive OOM. I try to findout what is the other object of same type and it is So far, I'm stuck. If somebody has other idea why OOM happens, please join |
|
Now after VS release @mousetraps please take a look. |
|
Does this occur even with the Analysis settings dialed back? |
|
Not clear what you asking @billti . just for inormation - I have Quick intellisense set. |
|
Yes, the 'Quick intellisense' is what I was referring to. If this is still happening for you on latest bits (and especially if with 'retail' rather than 'debug'), then if you can attach a repro we can investigate I'll take a look. Thanks. |
|
On the 1.1.RC on the Release I don't have OOM exception, looks like it is only for Debug bits. I will try to doublecheck with 1.1 RC2 too. There possibility that OOM is due to debug implementation of data structures in .NET which double memory allocations, but I don't 100% sure about this. Anyway, this is still indicates that too much memory is used for the Analysis information. I willing to debug this further, or if you have area which could indirectly helps, please route me to them. I willing to help and improve my development experience. |
|
I on release 1.1RC2 and seems I seeing this issue. The memory usage is go up to ~2Gb, then go back 1Gb. Nothing in the ActivityLog.xml, but not sure if something should appear here. Should I try with Debug build to check if I have any issue? VS2015, Quick Intellisense, NPM3 |
|
Maybe this is related. Often I see WER window popup which gather information about some error during working with VS. Don't know how to find what was cause. |
|
Are you on RC2 or RC2.1? What's the build number? |
|
I am on RC2.1 now, but this behavoiur was on even on 1.1. Whant to point, VS does not crash, it just freezes and WER start collecting data in the background, then VS unfreezes and I could continue working. So regarding that this is related to this issue is a bit speculative, based on fact that OOM is good candidate for WER and OOM also does not crash VS. I not 100% even sure that this is related to NTVS, but lately I work mostly with it, and no C# or other staff, so very likely that this is yours. I still does not manage to create my debug build, so I could double check that issue is still in place. |
|
On latest build. The VS was crashed |
|
@mousetraps as I told you, i could find more crashes for you 😄 |
|
@mousetraps Any news? What kind of information I have to give to you for this to be resolved? |
|
With latest bits and |
|
Two more OOM crashes at and one more at Any other information which I should provided for you - @mousetraps or @billti ? |
|
Crash happens for me with large amount of node modules, and it hangs trying to traverse the whole tree. To fix - turn off analysis either completely (VS / Tools / Options / TextEditor / Node / Intellisense) or put this into your .nsproj file: node_modules;jspm_packages;dist More info here: |
|
@DenisBiondic - could you please check out the ES6 Preview IntelliSense option and let us know if this helps address some of the perf issues you're running into? @kant2002 We're currently working on integrating Salsa for our IntelliSense experience going forward (behind the ES6 Preview flag) which should help address some of these perf issues. Closing this for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was working in the my gulp file when this error happens. I work on the dev + debug build.
Memory usage ~1.8Gb.
I create dump file, and will try to find out what take so much memory. Probably related to #44 and #264
The text was updated successfully, but these errors were encountered: