touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

** Also affects: mir/0.12
   Importance: Undecided
       Status: New

** Changed in: mir/0.12
    Milestone: None => 0.12.1

** Changed in: mir/0.12
       Status: New => Triaged

** Changed in: mir/0.12
   Importance: Undecided => High

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

** Changed in: mir (Ubuntu)
   Importance: Undecided => High

-- 
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:
  Triaged
Status in mir package in Ubuntu:
  Triaged

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