[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
** 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Fix Released Status in Mir 0.26 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2818 -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-artful-2806 -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783 -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736 ** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1 -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2683 -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
** Changed in: mir/0.26 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
This bug was fixed in the package mir - 0.26.1+17.04.20170209.1-0ubuntu1 --- mir (0.26.1+17.04.20170209.1-0ubuntu1) zesty; urgency=medium * New upstream release 0.26.1 (https://launchpad.net/mir/+milestone/0.26.1) - ABI summary: . mirclient ABI unchanged at 9 . mirserver ABI unchanged at 43 . mircommon ABI unchanged at 7 . mirplatform ABI bumped to 15 . mirprotobuf ABI unchanged at 3 . mirplatformgraphics ABI bumped to 12 . mirclientplatform ABI unchanged at 5 . mirinputplatform ABI unchanged at 6 . mircore ABI unchanged at 1 - Enhancements: . Support for MirBuffer API that allows for better management of hardware/software buffers. . Support for MirPresentationChain API that allows better control over {de}queueing of individual buffers {from}to the server. . Interim support for MirRenderSurface API that provides a unit of renderable for lower level content such as MirBufferStreams and MirPresentationChains, etc.. MirRenderSurface API is marked deprecated as it (and the relevant entry points) will be renamed to MirSurface before general availability. It will initially be used for revamping support for EGL drivers. . Synchronous version of mir_prompt_session_new_fds_for_prompt_providers() API (mir_prompt_session_new_fds_for_prompt_providers_sync()) added for convenience. . Better name for MirPersistentId-->MirWindowId. MirPersistentId has now been deprecated. - Bugs fixed: . [regression] Unity8 stutters constantly (like half frame rate). (LP: #1661128) . mir 0.26 - spinner loading animation, minimize, maximize too fast. (LP: #1661072) . [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] (LP: #1661508) . mir_window_request_persistent_id_sync seg faults when called twice. (LP: #1661704) . [regression] Windowed clients of nested servers are all black. (LP: #1661521) . Mir graphics platform ABI broke in series 0.26 but sonames never changed (LP: #1662455) . Fixes for 0.26 changelog. . [regression] mirscreencast hangs during screencast creation. (LP: #1662997) . libmirclient-dev missing build dependency on libmircore-dev. (LP: #1662942) . mir_window_spec_set_cursor_name() doesn't trigger mir::scene::SurfaceObserver::cursor_image_set_to. (LP: #1663197) . [regression] Software clients of nested servers are all black in Mir 0.25.0 and later. (LP: #1663062) -- Cemil AzizogluThu, 09 Feb 2017 21:46:32 + ** 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Fix Released Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
Fix committed to lp:mir/0.26 at revision 4007, scheduled for release in Mir 0.26.1 ** Changed in: mir/0.26 Status: In Progress => Fix Committed -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
** Changed in: mir Assignee: (unassigned) => Kevin DuBois (kdub) -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Fix Committed Status in Mir 0.26 series: In Progress Status in mir package in Ubuntu: Triaged Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2435 -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Fix Committed Status in Mir 0.26 series: In Progress Status in mir package in Ubuntu: Triaged Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 1.0.0 ** Changed in: mir Status: Triaged => Fix Committed -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Fix Committed Status in Mir 0.26 series: In Progress Status in mir package in Ubuntu: Triaged Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
** Branch linked: lp:mir/0.26 -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Triaged Status in Mir 0.26 series: In Progress Status in mir package in Ubuntu: Triaged Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
Why this crashes sometimes and other times spams is that wait_for_all() is sometimes called on a nullptr MirWaitHandle. The first thing that fn does is grab a lock. Some libc's seem smart enough to recognize that the memory isn't there and throw system_error, but its pretty conceivable that this could segfault if libc wasn't able to detect the memory issue and throw. -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Triaged Status in Mir 0.26 series: In Progress Status in mir package in Ubuntu: Triaged Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
yep, was the removal-of waithandle MP. needed some more checks before waiting for interval configuration. ** Changed in: mir/0.26 Assignee: (unassigned) => Kevin DuBois (kdub) ** Changed in: mir/0.26 Status: Triaged => In Progress ** Branch linked: lp:~kdub/mir/fix-1661508 -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Triaged Status in Mir 0.26 series: In Progress Status in mir package in Ubuntu: Triaged Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
As a workaround on zesty (0.26.0) you can use --nested-passthrough=OFF However that workaround stops being useful in lp:mir and lp:mir/0.26 because it will trigger bug 1661521. ** Description changed: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted - WORKAROUND: + *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF + Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Triaged Status in Mir 0.26 series: Triaged Status in mir package in Ubuntu: Triaged Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
Bisected somewhat. The flood of exceptions started here: revno: 3982 [merge] author: Brandon Schaefercommitter: Cemil Azizoglu branch nick: mir timestamp: Tue 2017-01-24 10:24:25 -0600 message: Deprecate mir_wait_for* I can't tell if that's different to the crash in the same function, or if it's just the same exception flood causing a crash in our release binaries... ** Changed in: mir Status: New => Triaged ** Changed in: mir/0.26 Status: New => Triaged ** Changed in: mir (Ubuntu) Status: New => Triaged ** Description changed: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () -from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 + from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () -from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 + from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () -from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 + from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () -from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 + from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () -from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 + from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () -from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 + from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) - at pthread_create.c:333 + at pthread_create.c:333 #9 0x7fccec4710ff in clone () - at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 + at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 + + However in development builds the server does not die and just floods + the log instead: + + [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error + std::exception::what: Operation not permitted + + [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error + std::exception::what: Operation not permitted + + [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error + std::exception::what: Operation not permitted + + [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error + std::exception::what: Operation not permitted WORKAROUND: Start your nested server with --nested-passthrough=OFF -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Triaged Status in Mir 0.26 series: Triaged Status in mir package in Ubuntu: Triaged Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? ()
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
** Summary changed: - Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] + [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] ** Tags added: regression -- 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/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: New Status in Mir 0.26 series: New Status in mir package in Ubuntu: New Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 WORKAROUND: Start your nested server with --nested-passthrough=OFF To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp