New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 642369 link

Starred by 0 users
Status: WontFix
Owner: ----
Closed: Sep 2016
Cc:
█ ranjitkan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Tabs seem to crash because of JavaScript execution.

Reported by patrik.m...@gmail.com, Aug 30 2016 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce the problem:
Reproduce using Telegram's web interface:
1. Open any chat.
2. Click the smiley in the upper-right corner of the text field.

Reproduce using Facebook:
1. Open a chat window (not 100 % sure if this triggers the crash every time).
- or -
1. Open one of the drop-down menus (also not 100 % sure if this works every time).

What is the expected behavior?

What went wrong?
Some JavaScript code leads tabs to crash.

Crashed report ID: 

How much crashed? Just one tab

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: 52.0.2743.116  Channel: dev
OS Version: 
Flash Version: 

This problem occurs since I updated Chromium this week – sadly I don't know what version I updated from.

If you don't manage to reproduce the behavior, I could find other ways to trigger it and/or trace what JavaScript code (on the websites) is responsible ...
chromium-crash.txt
4.3 KB View Download

Comment 1 by patrik.m...@gmail.com, Aug 30 2016 

Another way to reproduce using Google+:
1. Go to your Google+ profile.
2. Click "About".
3. Scroll.

This is btw a good example because (as you see, when you do so) you can see another thing I forgot to mention when I created this issue:
If a child-tab crashes, its parent-tab crashes too.

Comment 2 by patrik.m...@gmail.com, Aug 30 2016 

And yet another way to reproduce the bug using the Chrome Web Store:
1. Visit https://chrome.google.com/webstore/category/apps
2. Search for any string.
Note: If you reload after the crash you're not longer at the origin URL a further search will not trigger the crash.

Comment 3 by ranjitkan@chromium.org, Aug 31 2016

Cc: ranjitkan@chromium.org
Labels: Needs-Feedback
Could you please help us with any crash ID generated from chrome://crashes. As we are unable to reproduce the issue with the steps provided on chrome version 52.0.2743.116 on Ubuntu 14.04.

Thanks.!

Comment 4 by patrik.m...@gmail.com, Aug 31 2016 

Sadly, chrome://crashes says that crash reports are disabled and are not available for Chromium.
I'm running openSUSE Tumbleweed, btw

Comment 5 by patrik.m...@gmail.com, Sep 1 2016 

Just installed some updates, everything works fine now. Sorry for the effort! Issue can be closed now!

Comment 6 by ranjitkan@chromium.org, Sep 2 2016

Status: WontFix (was: Unconfirmed)
Thanks for the update, closing the issue as per above comment.!
►

Sign in to add a comment