xpra icon
Bug tracker and wiki

Opened 4 years ago

Closed 4 years ago

#1002 closed defect (duplicate)

OSX client periodically outputting "UI thread is now blocked" message, without any interaction occurring with the client local application menu

Reported by: alas Owned by: alas
Priority: minor Milestone: 0.16
Component: client Version: 0.15.x
Keywords: Cc:

Description

I'm not sure that this is really an issue for concern, but it has been increasingly catching my eye and making me wonder - so I thought I'd point it out.

I'm periodically seeing the combo message from the osx client expected with (and still being triggered by) interaction with the local application menu:

2015-10-14 10:30:42,028 UI thread is now blocked
2015-10-14 10:30:42,029 UI thread is running again, resuming

I'm often seeing it (as often as once a minute, or as rarely as once every 10 to 15 minutes) even when the xpra session applications are "completely inactive" (idle browser not even being moused over).

Running the client with -d osx doesn't seem to indicate any pattern (sometimes the output coincides with the timer_clipboard_check() increments, most times not).

Is there another flag worth trying? Is the client just periodically polling the new application menu to be sure all is in order? (I do notice that all the "Action" and such menu items have been moved into the "xpra" menu item, and re-ordered as sub menus, maybe that is causing this?)

Obviously, if this is something expected then just close this.

Change History (2)

comment:1 Changed 4 years ago by Antoine Martin

Owner: changed from Antoine Martin to alas

It's probably worth having a ticket recording this since it will often show up.
I am reluctant to hide the warning, because it is real and will cause us problems in other areas, so having it visible ensures that we now this is going on.
But I don't think there is much we can do about this.

Is the gap between the "blocked" and "running again" always this low? (here just 1ms)
If that's the case, maybe just printing something to the console is enough to cause it to wake up. (and maybe that's exactly what we'll do instead)

comment:2 Changed 4 years ago by Antoine Martin

Resolution: duplicate
Status: newclosed

Duplicate of #855, please add answers there.

Note: See TracTickets for help on using tickets.