New version of chrome breaks existing page / highcharts
Reported by
technomr...@gmail.com,
Oct 24 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36 Example URL: http://tech.akamai.com/api-visualization/ Steps to reproduce the problem: 1. Load the page 2. spinner never goes away 3. open the console you will see the error What is the expected behavior? The page should load normally and all charts should be displayed, however, it appears high charts no longer works What went wrong? The spinner never goes aways as one of the data sets canot be loaded. This was working in previous versions of chrome, i have had multiple people test to confirm. The error is as follows: Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? Yes the version right before this release. Does this work in other browsers? Yes Chrome version: 62.0.3202.62 Channel: stable OS Version: OS X 10.11.6 Flash Version: Uncaught TypeError: Cannot use 'in' operator to search for '0' in arguments_marker at forEach (<anonymous>) at a.each (highcharts.js:27) at l.drawTrackerGraph [as drawTracker] (highcharts.js:386) at l.render (highcharts.js:312) at highcharts.js:268 at Array.forEach (<anonymous>) at a.each (highcharts.js:27) at a.Chart.renderSeries (highcharts.js:268) at a.Chart.render (highcharts.js:270) at a.Chart.firstRender (highcharts.js:273)
,
Oct 25 2017
[mac bug triage] I'm not able to reproduce this on Chrome 62.0.3202.62. Does this still occur in a new profile? This can be tested by clicking the button at the very top-right button > Manage People > Add Person and navigating to your example URL with the new profile created.
,
Oct 25 2017
I am seeing this as well, in a different codebase (not highcharts). In our codebase (Asana), we have a large webapp, and we have an exception-logging mechanism to keep track of client-side errors that our users encounter. We have a large number of users. In the past couple of days, we have seen a sharp increase in the occurrence of this error. I am speculating that the recent general release of Chrome 62 is what caused the spike. This is definitely not consistently reproducible -- in fact I have not yet determined the repro steps. There seems to be a specific sequence of events that users must follow in order to hit this (it involves using a rich text editor in our product), but I have not determined the exact sequence of steps. The only difference for us vs. the above report is that the error message has a '1' instead of a '0'. In other words, this is the error: TypeError: Cannot use 'in' operator to search for '1' in arguments_marker This whole "arguments_marker" thing is interesting; some Google searches led me to find that v8 uses that name; see https://github.com/v8/v8/search?utf8=%E2%9C%93&q=arguments_marker&type= Looking through our logs, here are all the Chrome version numbers we have seen this in: 62.0.3197.0 62.0.3198.0 62.0.3199.0 62.0.3202.18 62.0.3202.29 62.0.3202.31 62.0.3202.38 62.0.3202.45 62.0.3202.52 62.0.3202.62 62.0.3202.8 62.0.3202.9 63.0.3205.0 63.0.3207.0 63.0.3212.0 63.0.3213.3 63.0.3214.0 63.0.3220.0 63.0.3221.0 63.0.3222.0 63.0.3223.0 63.0.3223.8 63.0.3225.0 Here is the complete list of OS versions our users have hit this on (these strings are pulled directly from the User-Agent strings) -- as you can see, this is across macOS, Windows, and Linux: Macintosh; Intel Mac OS X 10_9_5 Macintosh; Intel Mac OS X 10_10_5 Macintosh; Intel Mac OS X 10_11_0 Macintosh; Intel Mac OS X 10_11_5 Macintosh; Intel Mac OS X 10_11_6 Macintosh; Intel Mac OS X 10_12_0 Macintosh; Intel Mac OS X 10_12_4 Macintosh; Intel Mac OS X 10_12_5 Macintosh; Intel Mac OS X 10_12_6 Macintosh; Intel Mac OS X 10_13_0 Macintosh; Intel Mac OS X 10_13_1 Windows NT 10.0 Windows NT 10.0; Win64; x64 Windows NT 6.1 Windows NT 6.1; Win64; x64 Windows NT 6.3 Windows NT 6.3; WOW64 Windows NT 6.3; Win64; x64 X11; CrOS x86_64 9901.12.0 X11; CrOS x86_64 9901.29.0 X11; CrOS x86_64 9901.5.0 X11; Linux x86_64 None of our users have hit this on any browser other than Chrome. Given all of this, it seems very likely to me that there is some little edge case in recent versions of Chrome or V8 that is causing this. Here is a stack trace for one specific recent occurrence, including the path to our JS bundle which you can download (the JS is minified): [10-25 11:28:32.979][Error] TypeError: Cannot use 'in' operator to search for '1' in arguments_marker === Javascript Stack === at map (<anonymous>) at s.diff (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:343881) at e._trackDelta (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:362217) at e.applyDelta (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:358291) at t.updateContents (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:405576) at https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:3464338 at e._logTextChangePerf (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:3472582) at _handleQuillTextChange (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:3464218) at https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:3471975 at r.perform (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:227579) at Object.batchedUpdates (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:182008) at Object.i [as unstable_batchedUpdates] (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:209651) at s.<anonymous> (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:3471931) at https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:1449380 at s.runWithExceptionInfo (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:5007775) at t.a (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:1448422) at t.i.emit (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:338338) at t.emit (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:402538) at e.applyDelta (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:358884) at t.updateContents (https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:405576) at https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:398493 at https://d3ki9tyy5l5ruj.cloudfront.net/prod/compressed/build/bundles/f7df47c49f683b58096a271f3ee531d942d6e1af/apps/asana/bundle.js:1:315754
,
Oct 25 2017
By the way, for what it's worth, I have never been able to reproduce this myself -- not on the highcharts page referenced above, and not with Asana. I'm on Chrome "Version 62.0.3202.62 (Official Build) (64-bit)" on macOS Sierra 10.12.6.
,
Oct 25 2017
Unable to reproduce the issue on the reported chrome version stable 62.0.3202.0 and on the latest canary 64.0.3248.2 using Mac 10.12.6, Windows 10.12.6 and Ubuntu 14.04 with the following steps. 1. Opened chrome. 2. Navigated to the URL provided. 3. Opened console after page is loaded. We didn't find any error in the console. Attaching the screencast of the same. @Reporter: Could you please respond to comment#2 Thanks!
,
Oct 25 2017
Fix in-flight: https://chromium-review.googlesource.com/c/v8/v8/+/738176
,
Oct 25 2017
Wonderful, thank you!
,
Oct 31 2017
This issue still reproduces in Chrome version 62.0.3202.75 Can you please add more details on when fix will be applied to Chrome. https://bugs.chromium.org/p/chromium/issues/detail?id=779526#c4 |
||||
►
Sign in to add a comment |
||||
Comment 1 by manoranj...@chromium.org
, Oct 24 2017