[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure
This bug was fixed in the package mir - 0.8.1+15.04.20150112.2~rtm- 0ubuntu1 --- mir (0.8.1+15.04.20150112.2~rtm-0ubuntu1) 14.09; urgency=medium [ Daniel van Vugt ] * Bug fix release 0.8.1 (https://launchpad.net/mir/+milestone/0.8.1) - ABI summary: Servers need rebuilding, but clients do not; . Mirclient ABI unchanged at 8 . Mircommon ABI unchanged at 2 . Mirplatform ABI unchanged to 3 . Mirserver ABI bumped to 26.1 (due to breakage in LP: #1355173) - Fixes bugs: . Switching windows with a Trusted Prompt Session active loses the trusted prompt session (LP: #1355173) . a prompt session with an invalid application pid should be an error (LP: #1377968) * mir_demo_client_basic: Don't assert on user errors like failing to connect to a Mir server. It's much more useful to tell the user what they did wrong than to automatically generate error reports and duplicate apport bugs. (LP: #1331958) . (LP: #1331958) * Enable Project Butter motion event resampling and prediction for a more responsive touch experience. . * When the server disconnects unexpectedly, give the client SIGHUP instead of the present SIGTERM. The former is more appropriate because it indicates: Hangup detected on controlling terminal or death of controlling process [signal(7)] whereas SIGTERM is reserved for more polite user-requested shutdowns. . * Fix the common/shared source tree layout inconsistency. If it goes in libmircommon then it should be called common and not shared: * Move mir::time::*Clock out of libmirserver and into libmircommon. It will soon be used by libmirclient. * Bump version to 0.8.0 as Mir 0.7.0 was released today. * Remove dead code kill_client_processes() from mir_test_framework. * Work around spurious SIGKILL delivered to clients by Valgrind during tests. This is why CI is failing randomly (LP: #1364772) Actually this workaround is nothing new. A quick grep shows we already use the same hack in 13 other locations under tests/. . (LP: #1364772) * Privatise (don't install) headers that are unused by clients, QtMir or USC. This reduces the size of the public include/ tree from 377 to 121 files, and reduces the number of those that get installed from 208 to 121. * Bump the mircommon ABI to 2. We actually broke it in the Mir 0.7.0 release with symbols.map and didn't notice in time (LP: #1364890) (LP: #1364890) * Restore support for gcc-4.8/trusty (LP: #1366134) (LP: #1366134) * Publish an internal header that QtMir recently started using: mir/input/input_channel.h (LP: #1365934) . (LP: #1365934) * Relax dependencies on libmirplatform2. Any binary package that uses libmirplatform2 should already be ABI compatible with any version of libmirplatform2. Assuming we maintain our ABIs correctly... Minimising exact version requirements should minimise future package upgrade problems. . * Privatise more headers -- these are the ones unused by any external projects but are used internally by the server code in examples/ only. * Introducing a generic client performance report. Just turn it on: env MIR_CLIENT_PERF_REPORT=log yourclient and you will get nice useful performance information: [1409905806.508895] (II) perf: eglappsurface: 60.21 FPS, render time 0.62ms, buffer lag 47.64ms (3 buffers) [1409905807.510868] (II) perf: eglappsurface: 59.94 FPS, render time 0.13ms, buffer lag 49.96ms (3 buffers) [1409905808.513115] (II) perf: eglappsurface: 59.88 FPS, render time 0.12ms, buffer lag 49.98ms (3 buffers) . * Remove FPS output from examples/*. A more accurate and useful measure of FPS is now available to all clients by: env MIR_CLIENT_PERF_REPORT=log anyclient. * Privatise shared_library_prober*.h until such time that some external project needs them. * examples: Restore the -q (quiet mode) option to eglapps and flicker. It got deleted a little to hastily in r1906 when really it's still useful and worth keeping. . * Fix constructor syntax errors, which only just today g++ has decided are fatal (LP: #1369389) (LP: #1369389) * Introduce explicit driver ABI levels: libmirplatformNdriver, libmirclientMdriver * Bump the server ABI to 26. We broke it in r1924. * Build all platforms by default. No just Mesa. It's safe to do so, and in fact we already do so in our Deb builds :) This way no one can forget to fix Android build issues when working on desktop. . * Fix jerky/stuttering event delivery that could happen inside nested servers sometimes (LP: #1372300) (LP: #1372300) * Reduced visible input lag by approx one frame (on 59-60Hz displays)* * Avoid polling in a loop with timeout zero most of the time. That will only waste CPU. (LP: #1373809) (LP: #1373809) * demo shell: Keep colours consistent, regardless of the physical pixel format of
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure
** Branch linked: lp:ubuntu/utopic-proposed/mir -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure
This bug was fixed in the package mir - 0.7.0+14.10.20140829-0ubuntu1 --- mir (0.7.0+14.10.20140829-0ubuntu1) utopic; urgency=medium [ Daniel van Vugt ] * New upstream release 0.7.0 (https://launchpad.net/mir/+milestone/0.7.0) - Enhancements: . Test suite: Reworked mechanism to override Mir client functions . Demo shell: Detect custom rendering (decorations) to make it compatible with overlay optimizations . Make sure to preserve fd resources until the end of the sending of the message . Add test cases and script for tracking changes to the new ABIs: libmircommon, libmirplatform . Symbols file for libmirplatform . Symbols file for libmircommon . Symbols file for libmirserver . Various improvements to the SessionMediator test . Various build related improvements . Print testcase output during package build . Abort test when InProcessServer startup fails . Link the integration and unit tests against the server objects . Add a document detailing the useful tests to run and the useful logs to collect when troubleshooting a new android chipset . Enable motion event resampling and prediction for a more responsive touch experience. - ABI summary: Servers need rebuilding, but clients do not . Mirclient ABI unchanged at 8 . Mircommon ABI bumped to 1 . Mirplatform ABI bumped to 2 . Mirserver ABI bumped to 25 - API changes . Deleted function - frontend::Shell::create_surface_for(). If you have the std::shared_ptrfrontend::Session session, you can just do session-create_surface(params) instead to get a SurfaceId - Bug fixes: . Ensure we process lifecycle events before the nested server is torn down (LP: #1353465) . Fix race in InputTestingServerConfiguration (LP: #1354446) . Fix fd leaks in prompt session frontend code and tests (LP: #1353461) . Detect the additional things the demo shell draws on the renderable list and avoid calling the optimized post function if they are being drawn (LP: #1348330) . Client: Fix SIGTERM dispatch in our default lifecycle event handler (LP: #1353867) . DemoRenderer: Don't try to create a texture of width zero. (LP: #1358210) . Fix CI failures (LP: #1358698) . Fix build failure: variable ‘rc’ set but not used which happens in release mode when NDEBUG is set (LP: #1358625) . Only enumerate exposed input surfaces to avoid delivering events to occluded surfaces (LP: #1359264) . Android: do not post driver cancelled buffers (LP: #1359406) . Client: Ensure our platform library stays loaded for as long as it is needed by other objects (LP: #1358191) . Examples: Register the DemoCompositor with the Scene to properly process visibility events (LP: #1359487) . Mir_demo_client_basic: Don't assert on user errors like failing to connect to a Mir server (LP: #1331958) . Tests: Explicitly depend on GMock target to avoid build races (LP: #1362646) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 29 Aug 2014 16:12:54 + ** Changed in: mir (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure
** Changed in: mir/0.7 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure
** Changed in: mir Status: Fix Committed = Fix Released ** Changed in: mir Milestone: 0.8.0 = None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure
Fix committed to lp:mir/0.7 at revision 1880, scheduled for release in Mir 0.7.0 ** Changed in: mir/0.7 Assignee: (unassigned) = Alexandros Frantzis (afrantzis) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure
** Branch linked: lp:mir/0.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure
** Changed in: mir/0.6 Status: Triaged = Won't Fix ** Changed in: mir Milestone: 0.8.0 = 0.7.0 ** Changed in: mir/0.7 Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure
** Changed in: mir Milestone: 0.7.0 = 0.8.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect()
** Branch linked: lp:~afrantzis/mir/fix-1358191-connect-segv ** Changed in: mir Assignee: Daniel van Vugt (vanvugt) = Alexandros Frantzis (afrantzis) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect()
Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown ** Changed in: mir Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure
** Summary changed: - [regression] Clients are crashing (SIGSEGV) on mir_connect() + [regression] Clients are crashing (SIGSEGV) on mir_connect() failure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect()
** Changed in: mir Milestone: 0.7.0 = 0.8.0 ** Also affects: mir/0.7 Importance: Undecided Status: New ** Changed in: mir/0.7 Importance: Undecided = Critical ** Changed in: mir/0.7 Status: New = Triaged ** Changed in: mir/0.7 Milestone: None = 0.7.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect()
** Tags added: touch-2014-08-28 ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Importance: Undecided = Critical ** Changed in: mir (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect()
And today I can reproduce it again :) ii libmirclient8:armhf 0.6.1+14.10.20140814-0ubuntu1 armhf Display server for Ubuntu - client library current build number: 203 device name: mako channel: devel alias: ubuntu-touch/utopic last update: 2014-08-25 03:13:36 version version: 203 version ubuntu: 20140821.1 version device: 20140811.1 ** Changed in: mir Status: Triaged = In Progress ** Changed in: mir Assignee: (unassigned) = Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect()
Ugh. Ignore comment #6. I've finally got my phone in a state where I can reproduce the crash and it keeps happening even with r1834 reverted. Same problem, but apparently r1834 didn't cause it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect()
** Branch linked: lp:~vanvugt/mir/fix-1358191 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect()
Here's the valgrind output of the error from earlier in the day when I could reproduce it (on mako): ==8894== Invalid read of size 4 ==8894==at 0x4867B78: std::_Sp_counted_base(__gnu_cxx::_Lock_policy)2::_M_weak_release() (shared_ptr_base.h:190) ==8894==by 0x4866B39: std::__weak_count(__gnu_cxx::_Lock_policy)2::~__weak_count() (shared_ptr_base.h:755) ==8894==by 0x4866279: std::__weak_ptrmir::client::ClientPlatformFactory, (__gnu_cxx::_Lock_policy)2::~__weak_ptr() (shared_ptr_base.h:1350) ==8894==by 0x4866293: std::weak_ptrmir::client::ClientPlatformFactory::~weak_ptr() (shared_ptr.h:467) ==8894==by 0x48662D3: mir::CachedPtrmir::client::ClientPlatformFactory::~CachedPtr() (cached_ptr.h:28) ==8894==by 0x486E3F7: mir::client::DefaultConnectionConfiguration::~DefaultConnectionConfiguration() (in /home/phablet/mir/boom/lib/libmirclient.so.8) ==8894==by 0x486E441: mir::client::DefaultConnectionConfiguration::~DefaultConnectionConfiguration() (default_connection_configuration.h:46) ==8894==by 0x4855E8F: std::default_deletemir::client::ConnectionConfiguration::operator()(mir::client::ConnectionConfiguration*) const (unique_ptr.h:76) ==8894==by 0x4855941: std::unique_ptrmir::client::ConnectionConfiguration, std::default_deletemir::client::ConnectionConfiguration ::~unique_ptr() (unique_ptr.h:236) ==8894==by 0x4855071: (anonymous namespace)::DefaultMirConnectionAPI::connect(char const*, char const*, void (*)(MirConnection*, void*), void*) (mir_connection_api.cpp:75) ==8894==by 0x48552AB: mir_connect (mir_connection_api.cpp:140) ==8894==by 0x485530D: mir_connect_sync (mir_connection_api.cpp:156) ==8894== Address 0x5a92bf4 is not stack'd, malloc'd or (recently) free'd ==8894== ==8894== ==8894== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==8894== Access not within mapped region at address 0x5A92BF4 ==8894==at 0x4867B78: std::_Sp_counted_base(__gnu_cxx::_Lock_policy)2::_M_weak_release() (shared_ptr_base.h:190) ==8894==by 0x4866B39: std::__weak_count(__gnu_cxx::_Lock_policy)2::~__weak_count() (shared_ptr_base.h:755) ==8894==by 0x4866279: std::__weak_ptrmir::client::ClientPlatformFactory, (__gnu_cxx::_Lock_policy)2::~__weak_ptr() (shared_ptr_base.h:1350) ==8894==by 0x4866293: std::weak_ptrmir::client::ClientPlatformFactory::~weak_ptr() (shared_ptr.h:467) ==8894==by 0x48662D3: mir::CachedPtrmir::client::ClientPlatformFactory::~CachedPtr() (cached_ptr.h:28) ==8894==by 0x486E3F7: mir::client::DefaultConnectionConfiguration::~DefaultConnectionConfiguration() (in /home/phablet/mir/boom/lib/libmirclient.so.8) ==8894==by 0x486E441: mir::client::DefaultConnectionConfiguration::~DefaultConnectionConfiguration() (default_connection_configuration.h:46) ==8894==by 0x4855E8F: std::default_deletemir::client::ConnectionConfiguration::operator()(mir::client::ConnectionConfiguration*) const (unique_ptr.h:76) ==8894==by 0x4855941: std::unique_ptrmir::client::ConnectionConfiguration, std::default_deletemir::client::ConnectionConfiguration ::~unique_ptr() (unique_ptr.h:236) ==8894==by 0x4855071: (anonymous namespace)::DefaultMirConnectionAPI::connect(char const*, char const*, void (*)(MirConnection*, void*), void*) (mir_connection_api.cpp:75) ==8894==by 0x48552AB: mir_connect (mir_connection_api.cpp:140) ==8894==by 0x485530D: mir_connect_sync (mir_connection_api.cpp:156) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect()
** Branch linked: lp:~afrantzis/mir/fix-1358191-connect-segv-spike -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect()
The core issue seems to be that in this scenario the platform shared library is unloaded before the configuration object is being destroyed. The configuration object is holding a weak pointer to a shared pointer object (shared_ptr for the client platform factory) that was instantiated inside the platform library, and when the library is unloaded, type information and vtable for that shared pointer type vanishes too. When we try to destroy the weak_ptr we end up accessing memory that is invalid. I have proposed an MP that spikes a fix for this: https://code.launchpad.net/~afrantzis/mir/fix-1358191-connect-segv- spike/+merge/232108 by keeping the library loaded for as long as needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358191 Title: [regression] Clients are crashing (SIGSEGV) on mir_connect() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1358191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
