GNOME Bugzilla – Bug 773132
X Window System error: BadAlloc (insufficient resources for operation)
Last modified: 2017-01-31 23:11:05 UTC
I'm running Geary from git master on Ubuntu 16.10. If I visit a certain conversation, hit R (for Reply to All) and the begin typing, Geary dumps core with this message: === (geary:3188): Gdk-ERROR **: The program 'geary' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 42454 error_code 11 request_code 53 (core protocol) 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 GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped) === Mysteriously, this only happens for one certain conversation in my inbox - not others. I followed the advice in the message above and ran 'GDK_SYNCHRONIZE=1 gdb geary' to get a stack trace for this crash - see below. Unfortunately there are no function names for the stack frames in WebKit, since Ubuntu apparently doesn't offer debug symbols for that library.
+ Trace 236748
From the looks of the stack, this is probably the "Replying to very long emails" crasher introduced in Bug 765516, as noted in Bug 728002. I've just pushed commit d6ad54b with a work around (or you can just select some text in the message being replied to, so the reply window is smaller), but the proper fix will require the WK2 port to be in place.
This should be fixed properly on master by commit 29b339c - we are restricting the height of embedded composers by the size of the viewport they are in.