[Bug 564433] New: metacity crashes when searching for non-existant text in Google Chrome
http://bugzilla.novell.com/show_bug.cgi?id=564433 http://bugzilla.novell.com/show_bug.cgi?id=564433#c0 Summary: metacity crashes when searching for non-existant text in Google Chrome Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: jpryor@novell.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091103 SUSE/3.5.5-1.1.2 Firefox/3.5.5 After installing Google Chrome beta (version: 4.0.249.30), if I search for text within Chrome that does not exist in the document, metacity crashes. Reproducible: Always Steps to Reproduce: 1. Install Google Chrome: http://www.google.com/chrome/index.html?hl=en&brand=CHMA&utm_campaign=en&utm_source=en-ha-na-us-bk&utm_medium=ha 2. Start Chrome: /opt/google/chrome/google-chrome 3. In the initial "start" page, press Ctrl+F (find) and type "asdf" (no quotes) or some other text which doesn't exist in the page. Actual Results: Lots of window flicker, numerous running apps are minimized as metacity crashes and is automatically restarted. I know it's restarted as the pid from 'ps aux' is different. Before the search: jon 15436 1.1 0.4 346764 15240 ? Sl 10:15 0:00 /usr/bin/metacity After the search: jon 15640 0.3 0.5 347040 15616 ? Sl 10:23 0:00 /usr/bin/metacity Note that the pid is different. Expected Results: Obviously, metacity shouldn't crash, there shouldn't be tons of window flicker, and metacity's pid should remain the same. This was originally filed against Chrome, at: http://code.google.com/p/chromium/issues/detail?id=29723 I didn't realize until recently that the actual issue was in metacity (though Chrome makes the repro very easy). Based on the comments there, it also appears to be hardware-related, as it only happens to me, but not for others running the nVidia proprietary or Intel drivers. I'm running this on a Lenovo T60p laptop, 2.33GHz Core2 Duo, 64-bit. Video driver (from /sbin/lspci): 01:00.0 VGA compatible controller: ATI Technologies Inc M56GL [Mobility FireGL V5250] I'm running the openSUSE-provided (FOSS) ATI drivers, NOT the binary proprietary drivers. (Severity note: it's arguably Critical, as metacity is crashing, but since it auto-restarts I don't think it's that Critical. It is REALLY annoying, though.) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564433 http://bugzilla.novell.com/show_bug.cgi?id=564433#c1 --- Comment #1 from Jonathan Pryor <jpryor@novell.com> 2009-12-14 15:47:54 UTC --- Created an attachment (id=332451) --> (http://bugzilla.novell.com/attachment.cgi?id=332451) metacity-gdb.txt Attached gdb to metacity and then caused metacity to crash. Attached is the log file. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564433 http://bugzilla.novell.com/show_bug.cgi?id=564433#c2 --- Comment #2 from Jonathan Pryor <jpryor@novell.com> 2009-12-14 15:49:45 UTC --- The relevant part of the stack trace is: Thread 1 (Thread 0x7f49de56c7d0 (LWP 15640)): #0 0x00007f49da5684e5 in raise () from /lib64/libc.so.6 #1 0x00007f49da5699b0 in abort () from /lib64/libc.so.6 #2 0x00007f49db8c776f in g_assertion_message () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f49db8c7ce0 in g_assertion_message_expr () from /usr/lib64/libglib-2.0.so.0 #4 0x0000000000410ae4 in gdk_rectangle_intersect () #5 0x000000000041f05b in gdk_rectangle_intersect () #6 0x0000000000462696 in gdk_rectangle_intersect () So an assertion is failing. The message from ~/.xsession-errors: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window->frame != NULL) Apparently this is due to attempting to flash the window frame... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564433 http://bugzilla.novell.com/show_bug.cgi?id=564433#c3 --- Comment #3 from Jonathan Pryor <jpryor@novell.com> 2009-12-14 15:55:49 UTC --- As a workaround, we can disable flashing the window frame. Within gconf-editor, change the /apps/metacity/general/visual_bell_type value to 'fullscreen'. This causes the screen to flash when you type non-existent text into Chrome, but metacity doesn't crash. Returning this key value to 'frame_flash' "restores" the crashy behavior. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564433 http://bugzilla.novell.com/show_bug.cgi?id=564433#c4 Luis Medinas <lmedinas@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lmedinas@opensuse.org --- Comment #4 from Luis Medinas <lmedinas@opensuse.org> 2009-12-22 04:26:37 UTC --- I wonder if this is a metacity bug. I'm using chromium 4.0.260.0 and i can't reproduce this bug. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564433 http://bugzilla.novell.com/show_bug.cgi?id=564433#c5 --- Comment #5 from Jonathan Pryor <jpryor@novell.com> 2009-12-22 13:37:37 UTC --- @Luis: Did you set the GConf /apps/metacity/general/visual_bell_type key to "frame_flash"? As Comment 3 says, setting it to fullscreen removes the metacity crash. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564433 http://bugzilla.novell.com/show_bug.cgi?id=564433#c6 --- Comment #6 from Jonathan Pryor <jpryor@novell.com> 2009-12-22 13:39:22 UTC --- Also, Chrome needs to be using its custom frame thing -- Use System Title Bar and Borders should be *disabled*. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564433 http://bugzilla.novell.com/show_bug.cgi?id=564433#c7 Mingxi Wu <mxwu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mxwu@novell.com --- Comment #7 from Mingxi Wu <mxwu@novell.com> 2009-12-25 08:17:12 UTC --- Could you provide the ~/.xsession_errors, when metacity crashed? Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564433 http://bugzilla.novell.com/show_bug.cgi?id=564433#c Stephan Binner <binner@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jpryor@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564433 http://bugzilla.novell.com/show_bug.cgi?id=564433#c8 Jonathan Pryor <jpryor@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|jpryor@novell.com | --- Comment #8 from Jonathan Pryor <jpryor@novell.com> 2009-12-28 20:56:04 UTC --- As I said in Comment #2, the only relevant message in ~/.xsession_errors is: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window->frame != NULL) All surrounding messages came from other applications. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=564433 https://bugzilla.novell.com/show_bug.cgi?id=564433#c9 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |dimstar@opensuse.org Resolution| |FIXED --- Comment #9 from Dominique Leuenberger <dimstar@opensuse.org> 2012-07-31 20:40:12 UTC --- Sorry, this bug did not get the attention it deserved. Not likely, you have already upgraded to newer versions of openSUSE, which had a lot more bug fixes. We believe that this specific bug has been fixed during one of the release cycles; as such, I close the bug as 'FIXED'. Should you be able to reproduce this issue on a newer openSUSE version, please feel to report it again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com