pidgin/pidgin

Fix a crash when hovering over an exceptionally long URL (4074 characters,
release-2.x.y
2014-01-13, Mark Doliner
2bb66ef1475e
Fix a crash when hovering over an exceptionally long URL (4074 characters,
but it might be different for you) in a gtkimhtml widget (such as the IM
window).

This was reported on the support mailing list:
http://pidgin.im/pipermail/support/2013-March/012980.html
http://pidgin.im/pipermail/support/2013-March/012981.html

Repro steps:
1. "gdb pidgin"

2. "break gdk_x_error"
You'll probably need to type "y" to make breakpoint pending on future shared library load. (Or you could run first then add the breakpoint.)

3. "run --sync"
--sync probably isn't actually necessary. Theoretically it should make the backtrace more useful. Like, maybe it could actually show the Pidgin calls that trigger the problem? Or maybe the problem call starts from the gtk main loop, so there would never be Pidgin code in the backtrace? It's also possible we don't pass our args to the right places to make --sync work.

4. "cont"
I hit the breakpoint at startup for some reason. I've just been continuing past it. Doesn't seem to affect anything.

5. Open an IM window.

6. Paste a long URL.

7. Mouse over the long URL.

8. The breakpoint is hit.

9. "bt"

#0 gdk_x_error (display=0x740e30, error=0x7fffffffbc20)
at /build/buildd/gtk+2.0-2.24.13/gdk/x11/gdkmain-x11.c:458
#1 0x00007ffff73b94f6 in _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#2 0x00007ffff73b6741 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#3 0x00007ffff73b6785 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#4 0x00007ffff73b7378 in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#5 0x00007ffff73b2d3d in XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#6 0x00007ffff73b2dcb in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#7 0x00007ffff73b9e2f in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#8 0x00007ffff7395d14 in XCreatePixmap () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#9 0x00007ffff62bd0d2 in _gdk_pixmap_new (drawable=0x186ec60, width=width@entry=32774, height=25, depth=24,
depth@entry=-1) at /build/buildd/gtk+2.0-2.24.13/gdk/x11/gdkpixmap-x11.c:175
#10 0x00007ffff6289617 in IA__gdk_pixmap_new (drawable=drawable@entry=0x186ec60, width=width@entry=32774,
height=, depth=depth@entry=-1) at /build/buildd/gtk+2.0-2.24.13/gdk/gdkpixmap.c:249
#11 0x00007ffff6297036 in gdk_window_begin_implicit_paint (rect=0x7fffffffbed0, window=0x186ec60)
at /build/buildd/gtk+2.0-2.24.13/gdk/gdkwindow.c:2779
#12 gdk_window_process_updates_internal (window=0x186ec60) at /build/buildd/gtk+2.0-2.24.13/gdk/gdkwindow.c:5574
#13 0x00007ffff6299201 in IA__gdk_window_process_all_updates ()
at /build/buildd/gtk+2.0-2.24.13/gdk/gdkwindow.c:5696
#14 0x00007ffff6299269 in gdk_window_update_idle (data=)
at /build/buildd/gtk+2.0-2.24.13/gdk/gdkwindow.c:5322
#15 0x00007ffff6276e77 in gdk_threads_dispatch (data=0x1a45c40) at /build/buildd/gtk+2.0-2.24.13/gdk/gdk.c:512
#16 0x00007ffff53d8ab5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff53d8de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007ffff53d91e2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffff663ec77 in IA__gtk_main () at /build/buildd/gtk+2.0-2.24.13/gtk/gtkmain.c:1271
#20 0x0000000000499950 in main (argc=1, argv=0x7fffffffe538) at gtkmain.c:933

This is the message it prints when it exits:
The program 'Pidgin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 14454 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.)

I think it's kinda lame that gdk/gtk/xlib/whatever barfs when we give it a
ridiculously wide pango layout, but whatever. I'm assuming this problem is
gtkimhtml specific, and so I don't want to spend a whole lot of time fixing
it. As an easy fix I want to just truncate the URL displayed in the tooltip
to 200 characters.

Here's an example URL that I used to trigger the crash:
http://www.example.com/?%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%30123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789%3012345678901234567890123456789012345678901234567890123456789012345678
/** @page plugin-ids Plugin IDs
@section Introduction
Every plugin contains a unique identifier to prevent duplicate plugin
loading and conflicts. Third-party plugins (that is, plugins written by
anyone who is not a libpurple, Pidgin, or Finch developer) are expected
to use a plugin ID that follows a specific format. This format
categorizes plugins and makes duplicate IDs highly unlikely.
@section Format
The basic format of a plugin ID is as follows:
<tt><i>type</i>-<i>username</i>-<i>pluginname</i></tt>
The @em type indicator specifies the type of plugin. This must be one
of the following:
- core - A core libpurple plugin, capable of being loaded in any
program using libpurple. Core plugins may not contain any
UI-specific code.
- prpl - A protocol plugin. This is a special type of core plugin,
which provides libpurple the ability to connect to
another IM or chat network.
- lopl - A loader plugin, which loads scripts as plugins. Perl and
Tcl plugins are made possible by loader plugins.
- gtk - A GTK+ 2.x (a.k.a. Pidgin) plugin. These plugins may use
GTK+ code, but may not use window toolkit code, such as
X11, Win32, Cocoa, or Carbon.
- gtk-x11 - A GTK+ 2.x plugin that uses X11 code. These plugins may
use both GTK+ code and X11 code, allowing to hook into
features specific to X11.
- gtk-win32 - A GTK+ plugin that uses Win32 code. These plugins may use
both GTK+ code and Win32 code, allowing to hook into
features available on Windows.
- gnt - A GNT (a.k.a. Finch) plugin. These plugins may use GNT code.
- qpe - A plugin for the (now-abandoned) Qutopia user interface.
The @em username must be a unique identifier for you. It
@em should be your http://developer.pidgin.im Trac user ID. Failing that, you
could use your SourceForge user ID or your Freenode IRC nickname, if you
have either. The http://developer.pidgin.im Trac user ID is preferred.
Do @em not leave this field blank!
The @em pluginname is the name of your plugin. It is usually all
lowercase letters and matches the static plugin ID (the first argument to
the PURPLE_INIT_PLUGIN() macro call), although it can be anything you
like. Do @em not include version information in the plugin ID--the
#PurplePluginInfo structure already has a field for this.
@section nospaces One Last Rule for Plugin IDs
The last rule of plugin IDs is the most important of all. Plugin IDs may
@em NOT contain spaces. If you need a space, use another hyphen (-).
@section exceptions Exceptions to the Rule
As with any rule there are exceptions. If you browse through the source
tree you will see that the plugins we distribute with the Pidgin source
do not contain a username field. This is because while one developer may
have written each specific plugin, the plugins are maintained
collectively by the entire development team. This lack of a username
field is also an indicator that the plugin is one of our plugins and not
a third-party plugin.
Another exception to the rule is the <a
href="http://plugins.guifications.org/trac/wiki/PluginPack">Purple Plugin
Pack</a>. All plugins whose lives started in the Purple Plugin Pack use
<tt>"plugin_pack"</tt> for the username field to indicate origination in
the Purple Plugin Pack.
These two exceptions are mentioned here for completeness. We don't
encourage breaking the conventions set forth by the rules outlined above.
@section examples Examples of Well-Chosen Plugin IDs
The following is a list of well-chosen Plugin IDs listing a few good examples.
- <tt>"gtk-amc_grim-guifications"</tt> - This is the plugin ID for the
Guifications 2.x plugin.
- <tt>"gtk-rlaager-album"</tt> - This is the plugin ID for the Album
plugin, which is now part of the
Purple Plugin Pack. Its ID follows the
rules because its life started prior
to its inclusion in the Plugin Pack.
- <tt>"core-rlaager-irchelper"</tt> - This is the plugin ID for the IRC
Helper plugin, which is now part
of the Purple Plugin Pack. Its ID
follows the rules because its
life started prior to its
inclusion in the Plugin Pack.
@section plugin-db Plugin Database
Although it doesn't exist yet, in time there will be a plugin database
on the Pidgin website, where users can download and install new plugins.
Plugins will be accessed by your plugin ID, which is one reason why it
must be unique.
*/
// vim: syntax=c.doxygen tw=75 et