| No crash dump if system's crash reporting tool is enabled | ||||||||
| Reported by aocampo@chromium.org, Oct 7 2009 | Back to list | |||||||
Chrome Version : 4.0.221.8 (Official Build 28108) OS + version : Open SuSe 11 CPU architecture (32-bit / 64-bit): 64-bit window manager : Gnome 2.24.1 On my 64-bit open SuSe machine, I have 32-bit flash 10 installed but I can't get it to work. When I navigate to a page with flash, SuSe's bug buddy reporting tool quickly comes up and disappears. Here's the output from the console: testing@dhcp-172-22-193-85:/opt/google/chrome> 399a90b1-2e5d-9bd1-7d1f260b-32f3277e is dumped (bug-buddy:31926): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Failed to execute child process "minidump_dump" (No such file or directory) 68155f37-58ae-94f6-66cea1b1-2b67285a is dumped (bug-buddy:31939): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Failed to execute child process "minidump_dump" (No such file or directory) 5595468c-3240-2c93-0f5694fd-622e58e4 is dumped (bug-buddy:31951): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Failed to execute child process "minidump_dump" (No such file or directory) [31596:31596:3451265806649:ERROR:/usr/local/google/home/chrome-eng/b/slave/chrome-official-linux/build/src/chrome/browser/profile.cc(1064)] Not implemented reached in void ProfileImpl::CreatePasswordStore() 31ab198d-4410-a65d-21b527bf-51bdd8e8 is dumped (bug-buddy:31966): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Failed to execute child process "minidump_dump" (No such file or directory)
,
Oct 7 2009
Is this with the 32-bit RPM?
,
Oct 7 2009
Yes, with chrome 32-bit rpm.
,
Oct 9 2009
,
Oct 13 2009
Moving this out of mstone-4 and into mstone-5 after talking to the Linux team.
,
Oct 22 2009
Not sure if we want to fix this. 64-bit Chrome on OpenSUSE with 64-bit flash works pretty well for me.
,
Oct 22 2009
I think the particular crash (diagnosing 32-bit flash) we don't much care about, but the larger issue (not having SuSE intercept our crash dumps) we might want to fix if possible.
,
Oct 22 2009
It did not intercept crashes on my machine. Armine, can you retest?
,
Oct 22 2009
I am still seeing the issue with Chrome 4.0.223.5 (Official Build 29497)
,
Jan 6 2010
,
Jan 19 2010
this is the gtk module that gets injected: http://git.gnome.org/browse/bug-buddy/tree/gnome-breakpad/gnome-breakpad.cc#n451 It tests for this on startup: if (bugbuddy && !g_getenv ("GNOME_DISABLE_CRASH_DIALOG")) { I think we should set that environment variable for Google Chrome builds. What do you think?
,
Jan 19 2010
I couldn't reproduce this problem, but based on the gnome-breakpad code, I agree we don't want bug-buddy intercepting our crashes.
,
Jan 19 2010
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=36569
------------------------------------------------------------------------
r36569 | thestig@chromium.org | 2010-01-19 15:08:20 -0800 (Tue, 19 Jan 2010) | 5 lines
Changed paths:
M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/platform_util_linux.cc?r1=36569&r2=36568
Linux: Don't propagate $GNOME_DISABLE_CRASH_DIALOG to external apps.
BUG= 24120
TEST=none
Review URL: http://codereview.chromium.org/548071
------------------------------------------------------------------------
,
Jan 19 2010
Future Google Chrome releases will set $GNOME_DISABLE_CRASH_DIALOG=SET_BY_GOOGLE_CHROME in the /opt/google/chrome/google- chrome wrapper script.
,
Jan 26 2010
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=37041
------------------------------------------------------------------------
r37041 | thestig@chromium.org | 2010-01-25 13:20:53 -0800 (Mon, 25 Jan 2010) | 8 lines
Changed paths:
M http://src.chromium.org/viewvc/chrome/branches/302/src/chrome/common/platform_util_linux.cc?r1=37041&r2=37040
Merge 36569 - Linux: Don't propagate $GNOME_DISABLE_CRASH_DIALOG to external apps.
BUG= 24120
TEST=none
Review URL: http://codereview.chromium.org/548071
TBR=thestig@chromium.org
Review URL: http://codereview.chromium.org/546135
------------------------------------------------------------------------
,
Oct 12 2012
This issue has been closed for some time. No one will pay attention to new comments. If you are seeing this bug or have new data, please click New Issue to start a new bug.
,
Mar 10 2013
,
Mar 13 2013
|
||||||||
| ► Sign in to add a comment | ||||||||
Summary: No crash dump if system's crash reporting tool is enabled (was: NULL)