1232750 - Find all places that do a parse of source file in debugger and make sure they don't try on very large JS files

Status: RESOLVED WONTFIX

(DevTools :: Debugger, defect)

Description

[Brian Grinstead [:bgrins]]

Just as we fixed in Bug 1224726, we need to be careful to not use Parser.jsm on very large source files as it creates lot of memory usage and causes hangs.

Possible other uses:
* When the debugger is paused you can hover a variable and it'll show a tooltip of it's value
* When you cmd+click on a function thing to jump to the source

We can modify the new browser_dbg_sources-large.js test to cover these cases

Comment 1

[Brian Grinstead [:bgrins]]

Alternatively we could look into making Parser.jsm / Reflect.jsm not hang on these files

Comment 2

[Brian Grinstead [:bgrins]]

Or make the parse happen in a worker thread like pretty printing does.  Although in most of these cases the ux would require immediate feedback so waiting for the worker to finish is probably not an option.

Comment 3

[Jason Laster [:jlast]]

The debugger no longer uses parser.jsm so we should be alright.