(various) crashed with SIGSEGV in g_atomic_int_exchange_and_add()/g_variant_unref/?libappmenu.so/g_simple_async_result_complete

As you mentioned in your original bug description that you switched your font, does it only happen with that font or with other fonts too?

No it happens with the default configuration too (no ~/.vimrc)
The only file in ~/.vim is a file named .netrwhist and there is also the file .viminfo in $HOME
So nothing fantastic.

The only steps to reproduce are:
- From the command line run:
  $ gvim some_file
- Wait until it crashes (usually less then a minute)

I can reproduce it on 2 different system (a netbook and a laptop) with an up to date Natty.

I'm sorry for this poor report, let me know if and how I can gather more useful informations.

While I am able to reproduce it repeatedly on Unity, I didn't had a single crash when running the Classic Desktop.

I can confirm the last comment. I've been using the classic desktop for a while and today I tested Unity again.

While vim does not crash in the classic desktop, I can reproduce the crash every time under Unity.

bug 713192 looks like this one but for gnome-terminal.
I'm adding a task for dbusmenu because it seems involved somehow from the stacktrace.

Note that since the latest update update, I experience gnome-terminal crashes as well.

bug 713419 looks like this one but for nautilus. I'm also seeing the gnome-terminal bug as well.

confirmed due to comment #5 saying he also had same problem.

My log is also littered with application crashes all over (evince, gnome-terminal, eog, gvfs-smb, banshee, etc.) that seem to link back to libglib. And I am using the Classic desktop since I'm using a nouveau driver. Should I file separate bugs for each of these?

e.g.
[ 9479.287320] gnome-terminal[1927]: segfault at 24 ip 00007f7c163220b2 sp 00007fff93701c78 error 6 in libglib-2.0.so.0.2793.0[7f7c16309000+ed000]
[ 9504.078613] gnome-terminal[8133]: segfault at 24 ip 00007fd10aa360b2 sp 00007fff24467bd8 error 6 in libglib-2.0.so.0.2793.0[7fd10aa1d000+ed000]

Just had this problem during automated desktop testing with the character map (gucharmap) application

same problem in a fresh an up to date Natty VM with simple-scan

You can work around this temporarily by not loading the dbus menu proxy (UBUNTU_MENUPROXY=).

Could someone get a debug stacktrace?

the issue is not a vim one

bug #713281 has a debug retracing

debug stacktrace from the retracer:

"#0 0x00007f0c0196e0b2 in g_atomic_int_exchange_and_add (atomic=0x24, val=-1)
    at /build/buildd/glib2.0-2.27.93/glib/gatomic-gcc.c:29
No locals.
#1 0x00007f0c019d3cd2 in g_variant_unref (value=0x0)
    at /build/buildd/glib2.0-2.27.93/glib/gvariant-core.c:363
No locals.
#2 0x00007f0bf6e3c16d in register_application_window_cb (object=0x229c5c0,
    res=0x2497800, user_data=0x2355920) at bridge.c:324
 error = (GError *) 0x235bbc0
 context = (AppWindowContext *) 0x2355920
 variants = <value optimized out>
#3 0x00007f0c02cc22a2 in reply_cb (connection=0x2201120, res=0x248d8c0,
    user_data=<value optimized out>)
    at /build/buildd/glib2.0-2.27.93/gio/gdbusproxy.c:2109
 simple = (GSimpleAsyncResult *) 0x2497800
 value = <value optimized out>
 error = (GError *) 0x235bbc0
#4 0x00007f0c02cb7f54 in g_dbus_connection_call_done (
    source=<value optimized out>, result=<value optimized out>,
    user_data=0x25caac0)
    at /build/buildd/glib2.0-2.27.93/gio/gdbusconnection.c:3075
 connection = <value optimized out>
 state = (CallState *) 0x25caac0
 error = (GError *) 0x235bbc0
 reply = (GDBusMessage *) 0x0
 value = <value optimized out>
#5 0x00007f0c02c70fec in complete_in_idle_cb (data=0x24ae180)
    at /build/buildd/glib2.0-2.27.93/glib/gthread.h:347
 simple = <value optimized out>"

This bug was fixed in the package appmenu-gtk - 0.1.93-0ubuntu1

---------------
appmenu-gtk (0.1.93-0ubuntu1) natty; urgency=low

  * New upstream release.
    * Protect variant from being unref'd when NULL (LP: #703988)
    * Check to see if the item is already realized and parse
      immediately if it is.
 -- Ted Gould <email address hidden> Fri, 11 Feb 2011 09:40:27 -0600

Well it happened when i tried to resize a picture

Still happens to me when using Lyx

This bug is still present with appmenu-gtk 0.2.1-0ubuntu1

To reproduce it, simply move around in any GTK application's menus as rapidly as you can.

The bug seems to be a race condition. It is harder to reproduce with light-themes because they render the menu so slowly.

Cannot reopen this bug so I opened bug 763633.