Skip to content

tsserver crashed at OS level #1255

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ZuBB opened this issue May 10, 2017 · 9 comments
Closed

tsserver crashed at OS level #1255

ZuBB opened this issue May 10, 2017 · 9 comments
Labels

Comments

@ZuBB
Copy link

ZuBB commented May 10, 2017

just got this today

screen shot 2017-05-10 at 19 21 12

screen shot 2017-05-10 at 19 22 20

https://gist.github.com/ZuBB/f3f6074de207fdd4b1353c4bba3e38b5

I am not sure if we can get something from this but I believe we should have everything logged

@guncha
Copy link
Contributor

guncha commented May 10, 2017

Thanks for reporting! Yeah, not sure what can be done about this now, but let's see if other people are having similar issues.

@ZuBB
Copy link
Author

ZuBB commented May 17, 2017

got one more crash on same? subject https://gist.github.com/ZuBB/41111cf4b96cb164dcf5bd3608f8339b

@guncha
Copy link
Contributor

guncha commented May 17, 2017

Looks like an OOM (out of memory) error. You might have a better luck with a newer (or older) compiler version.

@ZuBB
Copy link
Author

ZuBB commented Jun 29, 2017

one crash but with different? msg

Typescript quit unexpectedly
Last output from tsserver:
node::Abort() [/Applications/Atom.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib]
 2: node::DLOpen(v8::FunctionCallbackInfo<v8::Value> const&) [/Applications/Atom.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib]
 3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/Applications/Atom.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/Applications/Atom.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib]
 5: v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [/Applications/Atom.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib]
 6: v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, v8::internal::JSMapIterator, 2>::EnsureGrowable(v8::internal::Handle<v8::internal::OrderedHashMap>) [/Applications/Atom.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib]
 7: v8::internal::Runtime_MapGrow(int, v8::internal::Object**, v8::internal::Isolate*) [/Applications/Atom.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib]
 8: 0x2a04b2a084e7
 9: 0x2a04b3e2000a
 

@guncha
Copy link
Contributor

guncha commented Jun 29, 2017

It's still an OOM error. Does it happen after you've been working for a while? Unless we're doing something bad like not closing files (which we are), this is a tsserver issue. If you're up for a good time, you can modify atom-typescript to pass --inspect to the tsserver process, connect to it with a debugger and poke around what's causing the memory bloat.

@ZuBB
Copy link
Author

ZuBB commented Jun 29, 2017

ok, sorry for a kind of dup. // busy to go with debug

@ZuBB
Copy link
Author

ZuBB commented Aug 18, 2017

hi there.

I think we have some good news for this. imo this is being caused by this microsoft/TypeScript#14628.

in ts repo there are couple of bug reports on same subject, but this seems to have most details and caused lots of investigation. although solution is still not found

@lierdakil
Copy link
Collaborator

For posterity:
Basically, the resolution seems to boil down to https://sandersn.github.io/manual/Workarounds-for-Out-of-Memory-Crashes.html, and if that doesn't help, file an issue on https://github.com/Microsoft/TypeScript

@github-actions
Copy link

This issue has been marked as stale because it did not have any activity for the last 90 days or more. Remove the stale label or comment or this will be closed in 14 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants