touch-packages team mailing list archive

Thread
Date

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

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Alan Griffiths <1433330@xxxxxxxxxxxxxxxxxx>
Date: Tue, 19 May 2015 13:43:24 -0000
Reply-to: Bug 1433330 <1433330@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: mir
       Status: Fix Committed => 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 Released
Status in Mir 0.12 series:
  Fix Released
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