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

Issue 763714 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
█ susanjuniab@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Segmentation fault at startup, even with temp-profile

Reported by kaef...@gmail.com, Sep 10 2017 
Chrome Version:
60.0.3112.113-0ubuntu0.16.04.1298


What steps will reproduce the problem?
(1) run on command line:
chromium-browser --verbose --temp-profile

What is the expected result?
working browser window

What happens instead?
cli prints the following, no window:
Using PPAPI flash.
--disable-new-tab-first-run --enable-user-scripts --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version=
/usr/bin/chromium-browser: line 230: 19195 Segmentation fault      $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@"


Please provide any additional information below. Attach a screenshot if
possible.
I'm using the latest chromium-browser package included in my distribution: Linux Mint 18.2 which is based on Ubuntu 16.04 (system details see https://gist.github.com/anonymous/8c8a7db628db4b468c3864a749e262a0 )

uname -a
Linux N550JV 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Comment 1 by susanjuniab@chromium.org, Sep 12 2017

Cc: susanjuniab@chromium.org
Labels: Needs-Triage-M60 TE-NeedsTriageFromMTV
kaefert@ Thanks for the issue.

Unable to reproduce the issue on Ubuntu 14.04 using version 60.0.3112.78 with the following steps.

1. Opened terminal and entered "chromium-browser --verbose --temp-profile".
2. Chromium browser is launched without any issues.

If reproducible, this looks specific to Ubuntu 16.04. Looping MTV team to check from their end if Ubuntu 16.04 is available there.

Thanks.

Comment 2 by kaef...@gmail.com, Sep 12 2017 

Hello susan,

Thanks for the reply!

I think we can close this issue - after a reboot the problem went away on it's own. I don't know why or what might have changed - I didn't install updates in between..

Regards,
Thomas

Comment 3 by divya.pa...@techmahindra.com, Sep 13 2017

Labels: Triaged-ET
Status: WontFix (was: Unconfirmed)
As per the above comments, after the reboot the issue does not persist any longer. Hence closing this issue as won't fix
►

Sign in to add a comment