Mir

Apps lock up when only one input thread

Bug #1274208 reported by Alan Griffiths
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
New
Undecided
Unassigned

Bug Description

On VT1 (say) run:
$ sudo bin/mir_demo_server_shell --ipc-thread-pool 1

On VT2 run:
$ sudo chmod a+rw /tmp/mir_socket
$ for x in bin/mir_demo_client_*; do ${x} -m /tmp/mir_socket& done

Start using Alt-Tab to switch applications and use Alt+cursor to rearrange apps so you can see multiple.

Expect:

Applications run normally (although perhaps with a reduced frame rate compared to a larger thread pool).

Actual:

Sometimes all the apps lock up. (If you continue tabbing they'll start again).

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

Possibly related to lp:1273224?

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

Server-side delays like this could be a big part of the problem:

[1391017285.282774] (II) frontend::MessageProcessor: mediator=0x7f922400cbf8: next_buffer(), elapsed=34484109µs

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Saturation of the thread pool is bug 1267323, regardless of what you set the number of threads to.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.