GNOME Bugzilla – Bug 604641
Massive tooltip causes a BadAlloc
Last modified: 2013-06-20 14:28:17 UTC
Created attachment 149791 [details] crasher -- hover the text In theory, apps should protect themselves from massive tooltips, but both Chrome and Epiphany crash if you make a page that has a tooltip that is too long. $ epiphany test.html The program 'epiphany-browser' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 2506 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
That test page doesn't crash any of Midori, Epiphany or Chromium on my system. Neither with GTK+ 2.18.5 nor git HEAD. So either your example is not correct or it was fixed already. What version of GTK+ did you test with?
(In reply to comment #1) > That test page doesn't crash any of Midori, Epiphany or Chromium on my system. > Neither with GTK+ 2.18.5 nor git HEAD. > > So either your example is not correct or it was fixed already. > > What version of GTK+ did you test with? I can very much crash ephy master/gtk+ master with this testcase...
Created attachment 151498 [details] demo showing the problem Hover the window
(test:1279): Gdk-WARNING **: Native Windows wider or taller than 65535 pixels are not supported The program 'test' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 555 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
$ dpkg -s libgtk2.0-0 | grep Version Version: 2.18.3-1ubuntu2.1 Ubuntu Karmic, compiz with default settings.
Confirming here: - GTK+ 2.19.3 - Epiphany 2.19.5 - Midori 0.2.2 - Chromium 4.0.249.30 All crashed with the testcase
*** Bug 607898 has been marked as a duplicate of this bug. ***
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 698758 ***