** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1333477
Title:
Fatal debug logging causes unnecessary crashes
Status in chromium-browser package in Ubuntu:
Fix Released
Bug description:
This is a simple one. It relates to these upstream bug reports
(dupes):
https://code.google.com/p/chromium/issues/detail?id=357473
https://code.google.com/p/chromium/issues/detail?id=371355
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1333477/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
