<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Wayland: Inspector GtkLabel drag'n'drop freezes gnome-shell session" href="https://bugzilla.gnome.org/show_bug.cgi?id=765062#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Wayland: Inspector GtkLabel drag'n'drop freezes gnome-shell session" href="https://bugzilla.gnome.org/show_bug.cgi?id=765062">bug 765062</a> from <a href="page.cgi?id=describeuser.html&login=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> Jonas Ådahl</a> <pre>(In reply to Carlos Garnacho from <a href="show_bug.cgi?id=765062#c6">comment #6</a>) > Comment on <a href="attachment.cgi?id=326672&action=diff" name="attach_326672" title="wayland: Handle wl_data_device being destroyed while focused">attachment 326672</a> <a href="attachment.cgi?id=326672&action=edit" title="wayland: Handle wl_data_device being destroyed while focused">[details]</a> <a href='review?bug=765062&attachment=326672'>[review]</a> [review] > wayland: Handle wl_data_device being destroyed while focused > > Indeed, makes sense. Funky that I wasn't able to reproduce (I only got the > protocol error), perhaps I was moving the cursor outside the client > altogether. I got only the protocol error when running mutter nested. Maybe we were "lucky" and it corrupted some irrelevant memory. The reason for the freeze was that, because the client was destroyed due to the error, the focus was lost, and the wl_list_remove() in the focus_out handler, pointing to memory that was not any of its business, happened to set the poll_fd GList in the gjs GC idle task source to an endless loop, and I guess when running nested mutter, it just happened to poke around in some memory not causing any visible errors.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>