New issue
Advanced search Search tips

Issue 730017 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Jun 2017
Cc:
rbyers@chromium.org
pfeldman@chromium.org
Components:
EstimatedDays: ----
NextAction: 2017-06-21
OS: Linux
Pri: 2
Type: Bug-Regression


Participants' hotlists:
Hotlist-1


Sign in to add a comment

[Violation] 'readystatechange' handler Halting script execution.

Reported by corin...@gmail.com, Jun 6 2017 
UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0

Steps to reproduce the problem:
1. Use Prototype JavaScript Version: '1.6.0.1'
1. Use an expensive function to an event handler
2. Dispatch that event
3. View the Developer Console (with verbose mode) for an error starting with "[Violation]"

What is the expected behavior?
Script working even with a simple info in the log

What went wrong?
The error "[Violation] 'readystatechange' handler took 186ms" was logged to the console and the rest of the script stopped executing.

Did this work before? Yes 56

Chrome version: 58.0.3029.81 (Versão oficial) 64 bits  Channel: stable
OS Version: 4.11.2-1-ARCH
Flash Version: Shockwave Flash 25.0.0.171
bug-screen.png
90.2 KB View Download

Comment 1 by rbyers@chromium.org, Jun 7 2017

Cc: pfeldman@chromium.org rbyers@chromium.org
Labels: Needs-Feedback
NextAction: 2017-06-21
This is similar to  issue 730017 .  But like that issue, this verbose-level console message should really be completely free from side effects - it's just a warning saying that the page did something unreasonably expensive.  If script is "halting" then that might be some other issue entirely unrelated.

Can you provide a reproduction (real site or test page) so we can debug this?

Comment 2 by monor...@bugs.chromium.org, Jun 21 2017 

The NextAction date has arrived: 2017-06-21

Comment 3 by tkent@chromium.org, Jun 26 2017

Status: Archived (was: Unconfirmed)
Feedback timeout
►

Sign in to add a comment