New issue
Advanced search Search tips

Issue 754155 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Frequent tab crashes since v60.0

Reported by m...@mkleinhans.de, Aug 10 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36

Steps to reproduce the problem:
1. Open a link to our website:

https://go.guidants.com/#c/506d44c5d3a5ab4701000001/%5B%5B%7B%22i%22%3A%22134001%22%7D%2C1%5D%2C%5B%7B%22chart%22%3A%22-2161918%22%7D%2C1%5D%5D

2. Click on the chart window in the middle of the screen.
3. Click on the Search-Icon in the toolbar that appeared, and type "SMA"
4. Click on the first result "SMA: Simple Moving Aver..."

5. Click and drag anywhere on an empty area in the chart to pan/scroll the visible area

=> Tab will crash very soon, sometimes even immediately after Step 4.

What is the expected behavior?
No crash

What went wrong?
Tab will crash very soon, sometimes even immediately after Step 4.

Did this work before? Yes 59

Chrome version: 60.0.3112.90  Channel: stable
OS Version: OS X 10.12.5
Flash Version: 

We have been running the current version of our charting component since last year, there have never been any issues until user started updating to v60.

Until now I was unable to find the exact cause of the issue; my guess right now is that it is related to some canvas functionality, as the crash does only occur in some specific charts.
We can reproduce it outside of our production website without the HTML UI around the canvas element, but it seems to happen much more frequently on a big page.

The issue does affect both windows and mac; we are receiving a lot of reports from our users.

Comment 1 by m...@mkleinhans.de, Aug 10 2017 

Here is the console output from a crash

#
# Fatal error in ../../v8/src/compiler/representation-change.cc, line 1074
# RepresentationChangerError: node #853:LoadElement of kRepFloat64 (NumberOrHole) cannot be changed to kRepTagged
#
0   Google Chrome Framework             0x000000010494d58c ChromeMain + 28328556
1   Google Chrome Framework             0x0000000107849feb ChromeMain + 77597899
2   Google Chrome Framework             0x000000010762958c ChromeMain + 75367020
3   Google Chrome Framework             0x0000000103d3d713 ChromeMain + 15680499
4   Google Chrome Framework             0x0000000103d68bab ChromeMain + 15857803
5   Google Chrome Framework             0x0000000103d5d46b ChromeMain + 15810891
6   Google Chrome Framework             0x0000000103d54e7c ChromeMain + 15776604
7   Google Chrome Framework             0x0000000103d54b4b ChromeMain + 15775787
8   Google Chrome Framework             0x0000000103d21aed ChromeMain + 15566797
9   Google Chrome Framework             0x0000000103d1f8f0 ChromeMain + 15558096
10  Google Chrome Framework             0x0000000103d1f7a7 ChromeMain + 15557767
11  Google Chrome Framework             0x0000000103c0f980 ChromeMain + 14444128
12  Google Chrome Framework             0x0000000103c0dc71 ChromeMain + 14436689
13  Google Chrome Framework             0x0000000103c0eb30 ChromeMain + 14440464
14  Google Chrome Framework             0x000000010494ddb1 ChromeMain + 28330641
15  Google Chrome Framework             0x00000001049b9114 ChromeMain + 28769780
16  Google Chrome Framework             0x00000001049b9643 ChromeMain + 28771107
17  Google Chrome Framework             0x00000001049b8db7 ChromeMain + 28768919
18  Google Chrome Framework             0x00000001049b4aef ChromeMain + 28751823
19  Google Chrome Framework             0x00000001049c4277 ChromeMain + 28815191
20  libsystem_pthread.dylib             0x00007fff9e81393b _pthread_body + 180
21  libsystem_pthread.dylib             0x00007fff9e813887 _pthread_body + 0
22  libsystem_pthread.dylib             0x00007fff9e81308d thread_start + 13

Comment 2 by m...@mkleinhans.de, Aug 10 2017 

It seems an issue does already exist for this crash, only found it now, sorry:
https://bugs.chromium.org/p/chromium/issues/detail?id=726554

Additionally, it seems like the issue can not be reproduced with current canary build (62.0.3181.0), probably due to the fix for #726554

Comment 3 by brajkumar@chromium.org, Aug 11 2017

Labels: Needs-Triage-M60
Status: WontFix (was: Unconfirmed)
As per comment #2 closing this issue, Please raise a new issue if you come across the similar one any of the latest chrome version.

Thanks!
►

Sign in to add a comment