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

Issue 617256 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jun 2016
Cc:
█ ashej...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Browser crashes on startup when using chrome://flags modified from default-installed settings

Reported by reginald...@gmail.com, Jun 3 2016 
Chrome Version       :  51.0.2704.79
URLs (if applicable) :  n/a
Other browsers tested:  n/a


(1)  use the exact same chrome://flags settings as attached in flags.html

(2)  Browser typically crashes on relaunch

(3)  Browser also crashes 20 % of the time when starting from a fresh, uninitialized state.

(4)  Suspect there are some chrome://flags settings which are overflowing the number of "--arguments" that can be passed to the Bash linux shell during chromium startup. OR possibly it is overflowing the number of words / characters that can be passed to execve?  i really cannot say for sure.  this speculation might be wrong.

(5)  Tested on Fedora version 23 with all updates.

(6)  systemd logs indicate that the error is happening at one or more of the following locations within Chrome / Chromium:
                         core.BrowserBlocking
                         core.Chrome_DBThread
                         core.Chrome_FileThred

(7)  I have attached coredump in coredump.txt


thank you
flags.html
399 KB View Download
coredump.txt
4.7 KB View Download

Comment 1 by ashej...@chromium.org, Jun 7 2016

Cc: ashej...@chromium.org
Labels: Needs-Feedback
Thanks for the report. Request you to please provide us with crash id from chrome://crashes ?

I really appreciate the help.

Thank you!

Comment 2 by ashej...@chromium.org, Jun 29 2016

Labels: -Needs-Feedback
Status: WontFix (was: Unconfirmed)
Marking the above issue as Wontfix, due to lack of user response. 
However, feel free to report a new issue if encountered with similar issue again with newer version of chrome. 

Thank you!
►

Sign in to add a comment