Closed
Bug 959408
Opened 11 years ago
Closed 9 years ago
don't print the contents of huge arrays
Categories
(DevTools :: Object Inspector, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1270179
People
(Reporter: nick, Unassigned)
Details
Attachments
(1 file)
2.83 KB,
application/zip
|
Details |
Example, an ImageData object. You can get such an object by calling createImageData on a CanvasRenderingContext2D instance. By clicking on a logged object, the box of values appears on the right, then freezes up FF. We probably should print all of the values of a huge array, or at least do so asynchronously.
Comment 1•11 years ago
|
||
Victor, don't we use paging for large arrays? Could it be that our heuristics need some more fine-tuning?
Component: Developer Tools → Developer Tools: Object Inspector
Comment 2•11 years ago
|
||
(In reply to Panos Astithas [:past] from comment #1)
> Victor, don't we use paging for large arrays? Could it be that our
> heuristics need some more fine-tuning?
Maybe we're missing something in our heuristics, definitely.
(In reply to Nick Desaulniers [:\n] from comment #0)
> Example, an ImageData object. You can get such an object by calling
> createImageData on a CanvasRenderingContext2D instance. By clicking on a
> logged object, the box of values appears on the right, then freezes up FF.
> We probably should print all of the values of a huge array, or at least do
> so asynchronously.
Nick, can you please post a small test-case? Also, more importantly, what version of Firefox are you running?
Reporter | ||
Comment 3•11 years ago
|
||
29.0a1 (2014-01-14)
See attached.
Reporter | ||
Comment 4•11 years ago
|
||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•