Fatal debug logging causes unnecessary crashes
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| chromium-browser (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
This is a simple one. It relates to these upstream bug reports (dupes):
https:/
https:/
Basically, the Chromium devs put a LOG(FATAL) in unofficial builds. So Chrome works fine, but not Chromium. The browser isn't actually crashing on its own, instead the LOG(FATAL) is killing the browser in order to get the attention of the user so they'll file a bug report. This sounds fine if it's a developer running the browser, but end users shouldn't have their browser crash because of an arbitrary FATAL log message.
The Ubuntu package should remove the LOG(FATAL) entirely so that the Chromium builds will work like the Chrome builds do, and not crash. The exact file/line/code is mentioned in the second bug report above.
| Changed in chromium-browser (Ubuntu): | |
| status: | New → Fix Released |
