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

Issue 798814 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

SEGV_MAPERR with tabs open from Atlassian

Reported by nat...@humanyze.com, Jan 3 2018

Issue description

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

Steps to reproduce the problem:
1. Go to Atlassian's hosted Jira
2. Wait
3. Boom

What is the expected behavior?
Not crashing

What went wrong?
The browser crashed, and wouldn't start up again.

Crashed report ID: no

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes Unsure - I hadn't updated Chromium since around August.

Chrome version: 62.0.3202.89  Channel: n/a
OS Version: Debian unstable (buster/sid)
Flash Version: 

In order to get the browser to run at all again, I had to delete the contents of .config/chromium/Default. I copied Bookmarks, "Login Data", and Cookies back in without problems, but if I just opened all the tabs I had open before (including the Jira and Confluence pages) it would crash after a minute or two.
 
chromium-crash
1.2 KB View Download
Cc: brajkumar@chromium.org
Labels: Needs-Milestone Needs-Feedback
nathan@ Are you able to reproduce this crash consistently? could you please provide sample crash Id's from chrome://crashes for further investigation.

Thanks!
I can reproduce it pretty consistently, though I won't have access to the computer it's on until Friday. There was nothing in chrome://crashes. It said "Crash reporting is not available in Chromium." when I looked while writing the bug report. Is there a switch for turning them on?
Status: WontFix (was: Unconfirmed)
Crash report not available.

Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.

Sign in to add a comment