Comment 7 for bug 1046068

If this bug is triggered in current stable (0.48.x) inkscape always leaves behind a temp file in $TMPDIR with the clipboard content in SVG format (some of the successfully saved output mime types based on the clipboard content temp file, also written to $TMPDIR, OTOH are cleaned up immediately after creation AFAICT, and failed attempts may result in additional zero-sized temp files).

The crash which now occurs in trunk instead seems to be triggered by the changes for bug #294354:
  <http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/11054>
since likely no more toplevel window is present at that point (Inkscape is crashing on exit, after having closed the document window). An empty (zero-sized) temp file is left behind in $TMPDIR after the crash.
AFAICT the crash occurs as soon as one (or more) output extensions are loaded from the shared or user extensions directory (irrespective of whether the extension itself would produce an error or not) - tested and reproduced by removing all output INX + script files from "$prefix/share/inkscape/extensions" and "$XDG_CONFIG_HOME/inkscape/extensions", and adding back the files for a randomly chosen output file type.

ISTM that Inkscape's system clipboard support needs to be adjusted to better support the (potentially only partially or differently implemented) GtkSelection and GtkClipboard features in the Quartz backend of current GTK+ 2.24.x (to prevent Inkscape from trying to export the clipboard content on exit at all).