Re: "force quit" dialog popping up during certain activities



I was able to ignore it on a previous release of DOTA 2 reborn, but it seems they've done a major version update and instead of waiting seconds before loading the game (where the dialog will eventually go away), it dialog seems to stay up indefinitely to the point where I can get into the game and see things moving around (albeit it with no mouse control).  

On Thu, Sep 17, 2015 at 9:25 AM, Jasper St. Pierre <jstpierre mecheye net> wrote:
Unfortunately, with the way OpenGL works, it likely has to do
intensive IO work on the main thread, texture uploads and shader
compiles and such, since there's currently no way to not block on
those.

You should be able to ignore the dialog until the game springs back to life.

On Thu, Sep 17, 2015 at 5:32 AM, drago01 <drago01 gmail com> wrote:
> On Thu, Sep 17, 2015 at 2:00 PM, Rui Tiago Cação Matos
> <tiagomatos gmail com> wrote:
>> On Sun, Sep 13, 2015 at 7:24 PM, Josh Stratton <strattonbrazil gmail com> wrote:
>>> I'm going to start investigating what criteria brings this dialog up,
>>
>> The dialog is triggered if the application advertises support for the
>> _NET_WM_PING protocol but then doesn't reply in time, see the wm
>> spec[1] .
>>
>> [1] http://standards.freedesktop.org/wm-spec/wm-spec-latest.html#idm140200472543696
>>
>>> but is
>>> there some way I disable this dialog?
>>
>> There's no supported way to disable it. Mutter uses the zenity command
>> to put up that dialog, so if you can hide that command from mutter or
>> make it non-executable, the dialog won't be launched but be aware that
>> this is an implementation detail and might change without notice so
>> you can't rely on it.
>>
>> Please get the application fixed or file a bug for mutter if you have
>> evidence that mutter isn't complying with the _NET_WM_PING protocol.
>
> This sounds like the app (DOTA 2) is doing excessive work (i/o) in the
> main thread (like loading files from disk) and can't reply to the ping
> request while doing so because its stuck waiting for the i/o to
> complete.
> So you should probably file a bug on there github instance.
> _______________________________________________
> gnome-shell-list mailing list
> gnome-shell-list gnome org
> https://mail.gnome.org/mailman/listinfo/gnome-shell-list



--
  Jasper
_______________________________________________
gnome-shell-list mailing list
gnome-shell-list gnome org
https://mail.gnome.org/mailman/listinfo/gnome-shell-list



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]