touch-packages team mailing list archive

Thread
Date

[Bug 1433330] Re: Some protobuf Closure objects can access dead objects

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <1433330@xxxxxxxxxxxxxxxxxx>
Date: Fri, 27 Mar 2015 00:13:38 -0000
Reply-to: Bug 1433330 <1433330@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This bug was fixed in the package mir - 0.12.1+15.04.20150324-0ubuntu1

---------------
mir (0.12.1+15.04.20150324-0ubuntu1) vivid; urgency=medium

  [ Alexandros Frantzis ]
  * New upstream release 0.12.1 (https://launchpad.net/mir/+milestone/0.12.1)
    - Bug fixes:
      . [regression] mali, powervr locks up with around the introduction or
        removal of a third overlay (LP: #1413211)
      . USC - mouse cursor on AMD graphics is drawing incorrectly
        (LP: #1417581)
      . mir_demo_server doesn't emit hover_exit events (LP: #1418569)
      . SessionMediator locks mutexes in one thread and unlocks them in
        another (LP: #1427976)
      . ProtobufResponder::send_response_result race (LP: #1428402)
      . Some protobuf Closure objects can access dead objects (LP: #1433330)
      . DisplayConfigurationOutput.physical_size_mm is undefined/zero
        (LP: #1430315)
      . vivid fails to build Mir as of 2015-03-22: error: #warning
        "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
        [-Werror=cpp] (LP: #1435127)
      . valgrind on armhf fails with with many errors (LP: #1435186)
 -- CI Train Bot <ci-train-bot@xxxxxxxxxxxxx>   Tue, 24 Mar 2015 16:09:54 +0000

** Changed in: mir (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1433330

Title:
  Some protobuf Closure objects can access dead objects

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  ProtobufMessageProcessor::dispatch will create a protobuf closure
  object that references the ProtobufMessageProcessor "this" pointer.

  The closure/callback object may be invoked by a different thread (e.g.
  SessionMediator::exchange_buffer). Since there's no protection there
  can be a race between dropping a connection (which destroys the
  ProtoBufMessageProcessor) and the callback being invoked by a
  compositor thread.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1433330/+subscriptions