Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Tern should be restarted after a timeout #8750

Closed
dangoor opened this issue Aug 13, 2014 · 2 comments
Closed

Tern should be restarted after a timeout #8750

dangoor opened this issue Aug 13, 2014 · 2 comments

Comments

@dangoor
Copy link
Contributor

dangoor commented Aug 13, 2014

To reproduce:

  1. Open a project with a problematic JS file (like that of Code hints: CPU stays at 100% with specific project, may eventually crash #7245)
  2. Open a file that shouldn't be a problem (like app.js in there)
  3. See the error dialog about the problem file (there are two in this project)
  4. You don't get code hints in app.js like you should (if you open another project and then reopen the melon project, the hints will work... note there is some delay because app.js is big).

I'm not sure what state Tern is in after a timeout, but I'm guessing that we need to restart the worker after a timeout.

@dangoor
Copy link
Contributor Author

dangoor commented Aug 25, 2014

Closing, because I don't think this is exactly the right description.

@dangoor dangoor closed this as completed Aug 25, 2014
@dangoor
Copy link
Contributor Author

dangoor commented Aug 25, 2014

I will open a new bug if I get a better reproducible case.

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

No branches or pull requests

1 participant