New issue
Advanced search Search tips

Issue 846437 link

Starred by 5 users

Issue metadata

Status: WontFix
Owner:
Closed: Sep 5
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug


Show other hotlists

Hotlists containing this issue:
Chromium


Sign in to add a comment

Can't open chromium 67-68 (kernel 4.17)

Reported by nevercmi...@gmail.com, May 24 2018

Issue description

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

Steps to reproduce the problem:
1. Open chromium with kernel 4.17
2. See dmesg logs
3. 

What is the expected behavior?
Open it

What went wrong?

Uhuuh, elf segment at 0000564cd7991000 requested but the memory is mapped already

Crashed report ID: is impossible :)

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Chrome version: 66.0.3359.181  Channel: beta
OS Version: 67.0.3396.56
Flash Version: 

Chromium 66 works fine (kernel 4.17)

Chromium 67 and 68 works FINE at older kernels (4.16)

My ram is fine (i've tested it with memtest86,   and if is a ram issue will happen at 4.16 too)

At 4.16 i can compile, render and work with chromium 68 without issues)

Chromium (dev/canary) gn rulefile https://p.teknik.io/PTQZX

Chromium beta rulefile https://p.teknik.io/a2LrW
 
Components: OS>Kernel
Labels: TE-NeedsTriageHelp
As it is Kernel logs related issue, adding respective component and seems it is out of scope from TE end. hence adding TE-NeedsTriageHelp to get it addressed from dev team.

Thanks..!
Status: WontFix (was: Unconfirmed)
Owner: thomasanderson@chromium.org

Sign in to add a comment