touch-packages team mailing list archive

[Kevin DuBois <kevin.dubois@xxxxxxxxxxxxx>]

ah, actually, looking at the backtrace again, disregard message #2...
looks different

** Changed in: mir
    Milestone: 0.18.0 => 0.19.0

-- 
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/1488232

Title:
  server shutdown failure (segfault)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  New

Bug description:
  Occasional shutdown segfault seen:

  Program received signal SIGSEGV, Segmentation fault.
  0xb6e3f3c6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  (gdb) bt
  #0  0xb6e3f3c6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb6b5f94e in __gnu_cxx::new_allocator<std::_Sp_counted_ptr_inplace<mir::frontend::detail::SocketMessenger, std::allocator<mir::frontend::detail::SocketMessenger>, (__gnu_cxx::_Lock_policy)2> >::deallocate (this=<error reading variable: Cannot access memory at address 0x1c>, 
      __p=<error reading variable: Cannot access memory at address 0x18>)
      at /usr/arm-linux-gnueabihf/include/c++/4.9.2/ext/new_allocator.h:110
  Backtrace stopped: previous frame inner to this frame (corrupt stack?)

  Happens more often when a client is actively sending messages (eg,
  swapping rapidly), and the server gets a SIGTERM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1488232/+subscriptions