Mir

nested Mir library calls next_buffer() during startup

Bug #1284739 reported by Alan Griffiths
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Medium
Alan Griffiths
Mir 0.1.7
mir (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

[tests on N4, but probably not restricted to android stack]

Start a host server:
   # ./mir_demo_server_basic --msg-processor-report log

Run a nested Mir application:
  # ./mir_demo_standalone_render_surfaces --host-socket /tmp/mir_socket --no-file surfaces-to-render 0
(and kill it after a second or two)

From the host see the log:
[1393348327.049628] (DD) frontend::MessageProcessor: mediator=0x4731de20, method=connect()
[1393348327.052894] (II) frontend::MessageProcessor: mediator=0x4731de20: connect(), elapsed=2350µs
[1393348327.101207] (DD) frontend::MessageProcessor: mediator=0x4731de20, method=create_surface()
[1393348327.132094] (II) frontend::MessageProcessor: mediator=0x4731de20: create_surface(), elapsed=29726µs
[1393348327.191029] (DD) frontend::MessageProcessor: mediator=0x4731de20, method=configure_display()
[1393348327.193257] (II) frontend::MessageProcessor: mediator=0x4731de20: configure_display(), elapsed=2044µs
[1393348327.250696] (DD) frontend::MessageProcessor: mediator=0x4731de20, method=next_buffer()
[1393348327.264705] (II) frontend::MessageProcessor: mediator=0x4731de20: next_buffer(), elapsed=13764µs
[1393348327.265285] (DD) frontend::MessageProcessor: mediator=0x4731de20, method=next_buffer()
[1393348327.274197] (II) frontend::MessageProcessor: mediator=0x4731de20: next_buffer(), elapsed=8240µs
[1393348327.279080] (DD) frontend::MessageProcessor: mediator=0x4731de20, method=next_buffer()
[1393348327.279507] (II) frontend::MessageProcessor: mediator=0x4731de20: next_buffer(), elapsed=274µs
[1393348331.024052] (DD) frontend::MessageProcessor: mediator=0x4731de20, method=release_surface()
[1393348331.034429] (II) frontend::MessageProcessor: mediator=0x4731de20: release_surface(), elapsed=9858µs
[1393348331.054572] (DD) frontend::MessageProcessor: mediator=0x4731de20, method=disconnect()
[1393348331.061378] (II) frontend::MessageProcessor: mediator=0x4731de20: disconnect(), elapsed=6622µs (disconnecting)

Note the three next_buffer() calls - these are from the compositor startup before the application intentionally displays anything.

mir_demo_server_basic in nested mode shows the same behaviour:

   # ./mir_demo_server_basic --host-socket /tmp/mir_socket --no-file

[1393348072.712012] (DD) frontend::MessageProcessor: mediator=0x4701de20, method=connect()
[1393348072.716346] (II) frontend::MessageProcessor: mediator=0x4701de20: connect(), elapsed=2929µs
[1393348072.764781] (DD) frontend::MessageProcessor: mediator=0x4701de20, method=create_surface()
[1393348072.789625] (II) frontend::MessageProcessor: mediator=0x4701de20: create_surface(), elapsed=24629µs
[1393348072.838397] (DD) frontend::MessageProcessor: mediator=0x4701de20, method=configure_display()
[1393348072.840655] (II) frontend::MessageProcessor: mediator=0x4701de20: configure_display(), elapsed=2014µs
[1393348072.913843] (DD) frontend::MessageProcessor: mediator=0x4701de20, method=next_buffer()
[1393348072.934017] (II) frontend::MessageProcessor: mediator=0x4701de20: next_buffer(), elapsed=19929µs
[1393348072.934322] (DD) frontend::MessageProcessor: mediator=0x4701de20, method=next_buffer()
[1393348072.942227] (II) frontend::MessageProcessor: mediator=0x4701de20: next_buffer(), elapsed=7721µs
[1393348072.946866] (DD) frontend::MessageProcessor: mediator=0x4701de20, method=next_buffer()
[1393348072.947751] (II) frontend::MessageProcessor: mediator=0x4701de20: next_buffer(), elapsed=518µs
[1393348076.598629] (DD) frontend::MessageProcessor: mediator=0x4701de20, method=release_surface()
[1393348076.604916] (II) frontend::MessageProcessor: mediator=0x4701de20: release_surface(), elapsed=5829µs
[1393348076.633910] (DD) frontend::MessageProcessor: mediator=0x4701de20, method=disconnect()
[1393348076.645599] (II) frontend::MessageProcessor: mediator=0x4701de20: disconnect(), elapsed=11384µs (disconnecting)

Tags: nested

Related branches

lp://staging/~alan-griffiths/mir/nested-sessions-dont-post-buffers-until-something-happens
PS Jenkins bot (community): Approve (continuous-integration)
Alexandros Frantzis (community): Approve
Alberto Aguirre (community): Approve
Diff: 344 lines (+135/-23)
5 files modified
examples/render_surfaces.cpp (+30/-2)
src/server/compositor/default_configuration.cpp (+7/-4)
src/server/compositor/multi_threaded_compositor.cpp (+27/-9)
src/server/compositor/multi_threaded_compositor.h (+5/-1)
tests/unit-tests/compositor/test_multi_threaded_compositor.cpp (+66/-7)
lp://staging/ubuntu/trusty-proposed/mir
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sounds just like bug 1281938. But certainly different.

tags: added: nested
Alan Griffiths (alan-griffiths)
Changed in mir:
assignee: nobody → Alan Griffiths (alan-griffiths)
status: New → In Progress
Daniel van Vugt (vanvugt)
Changed in mir:
milestone: none → 0.1.6
Daniel van Vugt (vanvugt)
Changed in mir:
milestone: 0.1.6 → 0.1.7
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown

Changed in mir:
status: In Progress → Fix Committed
Daniel van Vugt (vanvugt)
Changed in mir:
importance: Undecided → Medium
Daniel van Vugt (vanvugt)
Changed in mir:
status: Fix Committed → Fix Released
Changed in mir (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (3.3 KiB)

This bug was fixed in the package mir - 0.1.7+14.04.20140317.1-0ubuntu1

---------------
mir (0.1.7+14.04.20140317.1-0ubuntu1) trusty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.1.7 (https://launchpad.net/mir/+milestone/0.1.7)
    - mirserver ABI bumped to 17
    - mirclient ABI unchanged, still at 7. Clients do not need rebuilding.
    - Server API changes (AKA why doesn't my code build any more?):
      . Class "CompositingCriteria" has been removed. It's replaced by the more
        flexible "Renderable" interface. This also resulted in parameter
        changes for the Renderer and scene filtering classes.
      . The function "DisplayConfiguration::configure_output()" has been
        removed. Instead, please use the new mutable version of
        "DisplayConfiguration::for_each_output()" with which you can modify
        the output structure passed in on each iteration.
      . Exposed formerly private class "GLRenderer" and demonstrated how
        to override its behaviour in demo-shell. This area is under
        construction and may experience further major changes.
    - Added initial support for hardware (HWC) overlays to accelerate
      rendering and reduce power consumption. Not complete yet.
    - Screen rotation: Added mouse cursor rotation support, so you can now
      still control things on a rotated screen. Still missing rotation of
      the cursor bitmap itself.
    - Lots of fixes to support nested Mir servers (see below).
    - Major simplification to how surface size/position/transformation
      interact, making transformations much easier to manage and work with.
    - Bugs fixed:
      . ./cross-compile-chroot.sh: line 83: popd: build-android-arm: invalid
        argument popd: usage: popd [-n] [+N | -N] (LP: #1287600)
      . Key events sent to the wrong client (and delayed) (LP: #1213804)
      . Nested servers never receive input events (in their filters)
        (LP: #1260612)
      . Software clients crash immediately on nested servers - what(): Failed
        to mmap buffer (LP: #1261286)
      . MirMotionEvent lacks local coordinates. Reports only screen
        coordinates. (LP: #1268819)
      . Nested Mir crashes with - what():
        MesaNativePlatform::create_internal_client is not implemented yet!
        (LP: #1279092)
      . clients fail to find some libraries if mir installed via "make install"
        (LP: #1285566)
      . Nested server hangs with multimonitor and internal clients.
        (LP: #1287282)
      . [regression] Multi-monitor frame sync no longer works (not
        synchronized), and frames skip/jump/stutter (LP: #1288570)
      . Mir FTBFS: /usr/bin/ld: cannot find -lmirtestdraw (when cmake ..
        -DMIR_ENABLE_TESTS=OFF) (LP: #1283951)
      . nested Mir library calls next_buffer() during startup (LP: #1284739)
      . Building Mir produces lots of warnings from GLM headers about
        deprecated degrees values vs radians (LP: #1286010)
      . [enhancement] screencast of a single window (LP: #1288478)
      . Nexus4 + mir_demo_client_eglplasma starts to stutter after a while
        (LP: #1189753)
      . --host-socket documented default argument isn't...

Read more...

Changed in mir (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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