Issue 243941 in chromium: logging to the console becomes slower and slower as output accumulates

1 view
Skip to first unread message

chro...@googlecode.com

unread,
May 24, 2013, 8:13:22 PM5/24/13
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: Cr-Content-JavaScript Pri-2 Via-Wizard Type-Bug OS-Linux

New issue 243941 by matteosi...@gmail.com: logging to the console becomes
slower and slower as output accumulates
http://code.google.com/p/chromium/issues/detail?id=243941

UserAgent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.31 (KHTML, like
Gecko) Chrome/26.0.1410.63 Safari/537.31

Steps to reproduce the problem:
1. do a lot of console.log()'s from javascript while the console is open

What is the expected behavior?
The time it takes to do a single call to console.log() should stay constant.
If you have a javascript that does console.log() pretty often, and it is
smooth enough when it starts running, and it keeps doing the same amount of
logging with the same frequency, it should remain equally smooth and never
become jerky even after running for several hours (or days, for that
matter).

What went wrong?
As the length of the total output accumulated on the console grows, each
single call to console.log() becomes slower, and blocks the execution of
javascript code for a (initially very short) time that eventually becomes
even noticeable. That is, if you have some javascript code that does
console.log() pretty often, even if it is smooth at the beginning, after a
while it becomes jerky.

Did this work before? N/A

Chrome version: 26.0.1410.63 Channel: n/a
OS Version:


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

chro...@googlecode.com

unread,
May 24, 2013, 8:17:22 PM5/24/13
to chromi...@chromium.org

Comment #1 on issue 243941 by matteosi...@gmail.com: logging to the console
becomes slower and slower as output accumulates
http://code.google.com/p/chromium/issues/detail?id=243941

That is, console.log(someData) should take O(size(someData)). Instead, it
seems to take O(size(someData)+size(totalData)) where totalData is the
amount of data previously output to the console.
Reply all
Reply to author
Forward
0 new messages