New issue
Advanced search Search tips

Issue 670318 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Dec 2016
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Any site using the messenger javascript app from Intercom.com crashes upon loading the Intercom script.

Reported by jangc...@gmail.com, Dec 1 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2938.0 Safari/537.36

Steps to reproduce the problem:
1. Go to www.intercom.com or other site using the messenger service.
2. 
3. 

What is the expected behavior?
The page should load and the messenger component should show in the bottom right hand side.

What went wrong?
Greeted with an "Aw snap" error with no additional technical details.

Crashed report ID: 

How much crashed? Just one tab

Is it a problem with a plugin? N/A 

Did this work before? Yes 

Chrome version: 57.0.2938.0  Channel: canary
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 24.0 r0
Screen Shot 2016-12-01 at 11.19.37 AM.png
17.5 KB View Download

Comment 1 by jangc...@gmail.com, Dec 1 2016 

All extensions were disabled and browser cached was cleared prior to reporting the issue. Issue also reported to Intercom Support first, but posted here out of request from @googlechrome on Twitter.

Comment 2 by jangc...@gmail.com, Dec 1 2016 

Interestingly enough, the crash does not occur if Inspector is already opened. If you close Inspector after the page fully renders and then try to interact with rendered component the tab will crash. If you leave Inspector open you can interact with the component just fine.

Comment 3 by ccameron@chromium.org, Dec 1 2016

Labels: Needs-Feedback
Can you go to chrome://crashes/, and attach the crash report that you see?

Also, Canary can be very unstable, so double-check that the issue doesn't persist.

Comment 4 by ajha@chromium.org, Dec 2 2016

Labels: M-57

Comment 5 by jangc...@gmail.com, Dec 2 2016 

ccameron,

All that I see that I can provide is the ID of the crash report that I allowed to send:

Crash ID af1319ed-2d02-451c-adaa-4d978021a558 (Server ID: 475a02a300000000)

Let me know if there's something else I should be looking for. 

The crash is incredibly consistent. It's not specific to Intercom. I'm noticing similar crashes using Zendesk's agent page too, same troubleshooting process too... when inspector is open everything is fine and no consistent errors are showing in the console when the crash happens.

Comment 6 by ajha@chromium.org, Dec 2 2016

Labels: -Needs-Feedback
Mergedinto: 669968
Status: Duplicate (was: Unconfirmed)
Stack trace of the attached crash id 475a02a300000000 is same as the top crasher Issue 670175 on canary, hence merging into that.


This issue should be resolved in 57.0.2939.0.
►

Sign in to add a comment