New issue
Advanced search Search tips

Issue 918303 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Jan 2
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Frequent segfaults in Chrome_IOThread

Reported by anowlcal...@gmail.com, Dec 30

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3642.0 Safari/537.36

Steps to reproduce the problem:
1. Use Chrome normally; opening YouTube videos (especially while a video is already playing) frequently seems to cause this crash
2. Observe as the entire browser crashes
3. 

What is the expected behavior?
The browser shouldn't crash, especially not the whole browser.

What went wrong?
The whole browser crashes.

Crashed report ID: 69f7c80eec8372ca

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? Yes M72 or so?

Chrome version: 73.0.3642.0  Channel: dev
OS Version: Ubuntu 18.04
Flash Version: 

The browser will frequently crash several times in a row after it's crashed once and been reopened; closing several tabs quickly (before it crashes again) seems to decrease the likelihood of another crash.

On each crash, I get a line like these in dmesg:

[  484.159195] Chrome_IOThread[4387]: segfault at 0 ip 00007fde6459c5a1 sp 00007fde57d66738 error 4 in libc-2.27.so[7fde6440e000+1e7000]
[ 9799.621691] Chrome_IOThread[12182]: segfault at 0 ip 00007ff3c163f5a1 sp 00007ff3b4e09738 error 4 in libc-2.27.so[7ff3c14b1000+1e7000]
[13540.907292] Chrome_IOThread[29545]: segfault at 0 ip 00007faf39a195a1 sp 00007faf2d1e3738 error 4 in libc-2.27.so[7faf3988b000+1e7000]
[24522.851598] Chrome_IOThread[32229]: segfault at 0 ip 00007f476859d5a1 sp 00007f475bd67738 error 4 in libc-2.27.so[7f476840f000+1e7000]
[28050.149515] Chrome_IOThread[3953]: segfault at 0 ip 00007f6571e6a5a1 sp 00007f65656350c8 error 4 in libc-2.27.so[7f6571cdc000+1e7000]
[47638.565726] Chrome_IOThread[23147]: segfault at 0 ip 00007f78b63285a1 sp 00007f78a9af2e98 error 4 in libc-2.27.so[7f78b619a000+1e7000]
[52684.407012] Chrome_IOThread[17873]: segfault at 0 ip 00007f1d57a8f5a1 sp 00007f1d4b259e98 error 4 in libc-2.27.so[7f1d57901000+1e7000]
[53322.672159] Chrome_IOThread[7545]: segfault at 0 ip 00007f6a192ff5a1 sp 00007f6a0cac9e98 error 4 in libc-2.27.so[7f6a19171000+1e7000]

This crash has now happened many times, here are some crash IDs (I think they're all for the same crash):

69f7c80eec8372ca
2fbc885e261a51ce
808523adca839d9d
3395afe1c122da9d
865493ee61d10a0d
b7c788d64c87be81
 
Mergedinto: 915908
Status: Duplicate (was: Unconfirmed)
As per the above provided crash id, issue seems to be similar to #915908. Hence merging into it.Please feel free to undup if it is not similar.
Thanks..!
I don't have access to that issue unfortunately, so I can't say whether it's the same issue.

However, I found a page that will reliably crash the browser: http://technet.microsoft.com/en-us/sysinternals/bb896645 (other Sysinternals pages – change the number at the end of the URL – also cause a crash).

In fact, it looks like even the Sysinternals homepage does the same thing: http://technet.microsoft.com/en-us/sysinternals/

Crashes 83fcdf189f636161, aa06bb0d5552fb7c, d05abc63b7796c5e are all from those pages.

Sign in to add a comment