chromium-browser shutdown doesn't exit all processes

Bug #1257462 reported by Chad Miller on 2013-12-03
48
This bug affects 10 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Critical
Chad Miller

Bug Description

In a terminal, "--disable-extensions" makes it start and exit properly.

Disabling all extensions in the app manually does not exit properly.

The naive problem is that starting the browser makes white chrome and empty tabs.

There is no warning about locked profile as in https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1225215

Chad Miller (cmiller) on 2013-12-03
tags: added: lifecycle shutdown
Chad Miller (cmiller) wrote :

didrocks, thank you for your help on IRC. Will you please attach a listing of "ps xuwww |grep [c]hromium" after you ask chromium to shut down?

Also, is there a difference between closing the window with wm dismiss button, versus Shift+Control+Q, versus closing the last tab with tab management?

Also, suppose you have a window open, press Shift-Esc, and then use wm dismiss button to discard the main browser window. Does the process viewer remain?

Didier Roche (didrocks) wrote :

Hey Chad, thanks for looking at this, here are some testing:
* So, first, attaching the ps xuwww |grep [c]hromium results
* Secondly, yeah, the chrome process viewer stays (made a screenshot) when I'm closing with the wm button and shows that flash and drive are still up
* However, if I close chromium with Control + Shift + Q, no more process remains and all windows are closed.

So, does a background page (maybe the google drive one? But it's not in my extension list) would force the browser to not stop?

Didier Roche (didrocks) wrote :
Detlef Bieritz (detlef-bieritz) wrote :

hi. i have the same problem.
if i logon to chromium "in Chromium anmelden" the processes stay,
if i logoff from chromium "von Chromium abmelden" the processes end.

delete profile: no change
reinstall chromium 'apt-get --reinstall install chromium-browser': no change
chromium purge and new install: no change

exact the same prob in google chrome since the last update chromium & chrome

Detlef Bieritz (detlef-bieritz) wrote :

now repeatedly tested, i think there's the problem
logoff: all ok
logon: sleeping processes - and chrash when chromium new started

chrome also

Detlef Bieritz (detlef-bieritz) wrote :

workaround: chromium-browser --disable-background-networking
processes end
tested with chromium & chrome

crystal (crystalmanous) wrote :

thanks

crystal (crystalmanous) wrote :

The attachment "dropbox.pyc" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Arno (idfafp) wrote :

Hi, maybe it's a stupid question, but isn't it the normal behavior of Chromium/Chrome ?

There is an item at the bottom of the Chromium settings page, that lets you choose if Chromium will continue running in background after you close it.

Changed in chromium-browser (Ubuntu):
assignee: Chad Miller (cmiller) → SYEDFAYAZ MUJAWAR (syedfayaz28)
assignee: SYEDFAYAZ MUJAWAR (syedfayaz28) → nobody
Chad Miller (cmiller) on 2015-10-02
Changed in chromium-browser (Ubuntu):
assignee: nobody → Chad Miller (cmiller)

Some testing on odroid C2:

Chromium browser with no extensions:
droid@odroid64:~$ chromium-browser --disable-extensions
Gtk-Message: Failed to load module "gail"
Gtk-Message: Failed to load module "atk-bridge"
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "topmenu-gtk-module"
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
xdg-settings: invalid operation
Try 'xdg-settings --help' for more information.
Segmentation fault
odroid@odroid64:~$ [3:3:0100/000000:FATAL:zygote_linux.cc(510)] Check failed: len > 0 (0 vs. 0)
#0 0x0000f42cd7c2 base::debug::StackTrace::StackTrace()
#1 0x0000f42e074a logging::LogMessage::~LogMessage()
#2 0x0000f64e72c2 <unknown>
#3 0x0000f64e79dc <unknown>
#4 0x0000f64e7b9e <unknown>
#5 0x0000f64e7e88 <unknown>
#6 0x0000f64e819a <unknown>
#7 0x0000f64e8f04 <unknown>
#8 0x0000f6280222 <unknown>
#9 0x0000f62806fc <unknown>
#10 0x0000f627ffd2 content::ContentMain()
#11 0x0000ab38e430 <unknown>
#12 0x0000f29268aa __libc_start_main

Received signal 6
#0 0x0000f42cd7c2 base::debug::StackTrace::StackTrace()
#1 0x0000f42cdaac <unknown>
#2 0x0000f2935260 <unknown>
#3 0x0000f2926af6 <unknown>
#4 0x0000f2934638 gsignal
#5 0x0000f293533a abort
[end of stack trace]
[21793:21793:0330/191623:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process

Chromium Browser started with sudo:
odroid@odroid64:~$ sudo chromium-browser
[1:1:0330/190058:FATAL:setuid_sandbox_client.cc(126)] Check failed: IsFileSystemAccessDenied().
#0 0x0000f44e37c2 base::debug::StackTrace::StackTrace()
#1 0x0000f44f674a logging::LogMessage::~LogMessage()
#2 0x0000f3a742ae sandbox::SetuidSandboxClient::ChrootMe()
#3 0x0000f66fede0 <unknown>
#4 0x0000f6496222 <unknown>
#5 0x0000f64966fc <unknown>
#6 0x0000f6495fd2 content::ContentMain()
#7 0x0000ab328430 <unknown>
#8 0x0000f2b3c8aa __libc_start_main

Received signal 6
#0 0x0000f44e37c2 base::debug::StackTrace::StackTrace()
#1 0x0000f44e3aac <unknown>
#2 0x0000f2b4b260 <unknown>
#3 0x0000f2b3caf6 <unknown>
#4 0x0000f2b4a638 gsignal
#5 0x0000f2b4b33a abort
[end of stack trace]

Chromium Browser started as a regular user:
droid@odroid64:~$ chromium-browser
Gtk-Message: Failed to load module "gail"
Gtk-Message: Failed to load module "atk-bridge"
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "topmenu-gtk-module"
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
getrlimit(RLIMIT_NOFILE) failed
Segmentation fault
odroid@odroid64:~$ [21225:21225:0330/190735:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process

I saw the frame of the browser come up for a fraction of a second before disappearing when starting it as a regular user.
Let me know if there is anything else that would help with diagnosis.

Dave

Changed in chromium-browser (Ubuntu):
status: Confirmed → Fix Committed
status: Fix Committed → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers