Unity & chrome crash on DRI 300 radeon

[David Barth]

Using Chrome inside Unity, and quite often the HTML "select" boxes trigger a crasher when the popup is dismissed.
To reproduce: go to a bug report on launchpad, where you have sufficient rights to change the status of the bug, use the "classic interface" where the status is changed with an HTML dropdown selector.

[David Barth (dbarth)]

Stack trace with debug symbols loaded.

[David Barth (dbarth)]

This seems not to be strictly a Unity issue, but more one in the radeon DRI driver.

[David Barth (dbarth)]

Marking invalid for now, but feel free to reopen on unity if necessary.

[David Barth (dbarth)]

@raof: can you take a look and assign to the proper mesa/dri project for tracking the issue?

[Omer Akram (om26er)]

I face the same issue on intel bug 660124

[Chris Halse Rogers (raof)]

Ok. It looks like something is triggering an assert() in mesa. This is probably a mesa bug, shuffling off there.

This crash should be printing out some reason for the assert; it would be useful if you could attach it.

[David Barth (dbarth)]

This is what i see just before the error:

Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Window manager warning: Log level 128: Active window is: NULL
Window manager warning: Log level 128: Switching to menus from XID 0
Window manager warning: Log level 16: gtk_menu_detach(): menu is not attached
Window manager warning: Log level 128: Looking for parent window on XID 77788022
Window manager warning: Log level 128: Switching to menus from XID 77788022
Window manager warning: Log level 128: Unable to get MWM functions for: 77788022
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(mutter:5522): libunity-DEBUG: unity-appinfo-manager.vala:149: Monitoring extra app directory: file:///home/dbarth/.local/share/applications
Bug in window manager: Unexpected X error: BadDamage (invalid Damage parameter) serial 7449 error_code 168 request_code 153 minor_code 3)
Aborted

[David Barth (dbarth)]

So it's the BadDamage that is not trapped and provokes the abort in mutter.
But what I don't see is why the BadDamage reaches us, and why it's triggered by the radeon driver.

[Omer Akram (om26er)]

my logs from the duplicate bug report https://bugs.edge.launchpad.net/ubuntu/+source/unity/+bug/660124/+attachment/1691455/+files/unity.txt though I still have to install debug symbols to get a new backtrace