Open
Bug 1281960
Opened 8 years ago
Updated 2 years ago
console.log loses track of updates in large loops
Categories
(DevTools :: Console, defect, P3)
Tracking
(firefox50 affected)
NEW
Tracking | Status | |
---|---|---|
firefox50 | --- | affected |
People
(Reporter: emceeaich, Unassigned)
Details
(Whiteboard: [console-rewrite-fix])
Attachments
(1 file)
28.42 KB,
image/png
|
Details |
Run this in console: for (let i = 0; i < 10000; i++) { console.log(typeof null == 'undefined'); } I expected to see: `false (10000)` but got: `false (4677)` see attachment
Comment 1•8 years ago
|
||
The output can end up getting messages removed do to the batching and pruning that happens because of performance issues in the frontend. When a message is sent, it's queued up and all of them get sent for rendering after N ms (20). But if there are more messages than will be displayed in the frontend at once (1000, I think) then it ends up discarding them before attempting to render. All of this happens before any repeat checking and so we end up skipping messages. Definitely a bug, since in this case the messages that are not meant to ever be seen actually end up changing the display of one that does (by incrementing the repeat bubble). But it's in a bit of a tricky and performance sensitive piece of code so isn't likely to get fixed in the current frontend. Luckily the work in progress of the console rewrite (started in Bug 1260283 but still preffed off) is properly showing 10000 messages in the bubble so we'll keep this open and revisit it when that work is complete.
Priority: -- → P3
Updated•8 years ago
|
Whiteboard: [console-rewrite-fix]
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•