chromium-browser shutdown doesn't exit all processes
Bug #1257462 reported by
Chad Miller
This bug affects 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Fix Released
|
Critical
|
Chad Miller |
Bug Description
In a terminal, "--disable-
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:/
tags: | added: lifecycle shutdown |
Changed in chromium-browser (Ubuntu): | |
assignee: | Chad Miller (cmiller) → SYEDFAYAZ MUJAWAR (syedfayaz28) |
assignee: | SYEDFAYAZ MUJAWAR (syedfayaz28) → nobody |
Changed in chromium-browser (Ubuntu): | |
assignee: | nobody → Chad Miller (cmiller) |
Changed in chromium-browser (Ubuntu): | |
status: | Confirmed → Fix Committed |
status: | Fix Committed → Confirmed |
tags: | removed: patch |
To post a comment you must log in.
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?