lp://qastaging/mir/0.19
- Get this branch:
- bzr branch lp://qastaging/mir/0.19
Branch merges
- Daniel van Vugt: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 87 lines (+25/-1)4 files modifiedCMakeLists.txt (+1/-1)
debian/changelog (+12/-0)
src/platforms/android/server/real_hwc_wrapper.cpp (+10/-0)
src/platforms/android/server/real_hwc_wrapper.h (+2/-0)
Branch information
Recent revisions
- 3293. By Alan Griffiths
-
Workaound for g++ 4.x bug where std::uncaught_
exception( ) unexpectedly returns true Cherry picked from lp:mir r3299
- 3292. By Andreas Pokorny
-
input: Copy output rectangles when configuration changes
DisplayInputRegion used to calculate a set of rectangles on every mouse event, even when the set of outputs rarely changes. This change keeps a mir::geometry:
:Rectangles as cache. The actual dead lock of lp:1538632 was caused by the fact that DisplauInputRegion would use - to calculate the mir::geometry: :Rectangles - the following locks in the given order:
* mir::graphics::Display: :configuration_ mutex via for_each_ display_ sync_group( )
* mir::graphics::DisplayGroup: :guard via for_each_ display_ buffer( ) Simultaneously the SystemWindowMan
ager::add_ display method is called by the CompositingFunctor, which uses DisplaySyncGrou p::for_ each_display_ buffer, and deeper in the call tree GraphicsDisplay Layout would request a copy of the DisplayConfigur ation during place_in_output, which results in the reverse lock ordering:
* mir::graphics::DisplayGroup: :guard via for_each_ display_ buffer( )
* mir::graphics::Display: :configuration_ mutex via configration() This change makes sure that the DisplayInputRegion does not touch any locks used by the graphics platform during input event handling
Cherry picked from lp:mir r3288
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://qastaging/mir