Activity log for bug #1350825

Date Who What changed Old value New value Message
2014-07-31 12:07:10 Alexandros Frantzis bug added bug
2014-07-31 12:07:10 Alexandros Frantzis attachment added One instance of a SEGV https://bugs.launchpad.net/bugs/1350825/+attachment/4166650/+files/unity-stop-backtrace.txt
2014-07-31 12:07:39 Alexandros Frantzis attachment added Another instance of a SEGV https://bugs.launchpad.net/unity8/+bug/1350825/+attachment/4166651/+files/unity-stop-backtrace1.txt
2014-07-31 12:08:41 Alexandros Frantzis description Steps to reproduce: 1. Start app (e.g. calculator) 2. From phablet-shell run 'stop unity8' Expected result: unity8 shuts down properly Actual result: unity8 often (but not always) crashes with a SEGV I have attached thread backtraces of two crash instances. Note that the SEGV site is different in those traces, which indicates that this a race (also reinforced by the fact that the crash doesn't happen always). Setting to high as this may affect our tests. Steps to reproduce: 1. Start app (e.g. calculator) 2. From phablet-shell run 'stop unity8' Expected result: unity8 shuts down properly Actual result: unity8 often (but not always) crashes with a SEGV I have attached thread backtraces of two crash instances. Note that the SEGV site is different in those traces, which indicates that this a race (also reinforced by the fact that the crash doesn't happen always). In both cases the SEGV occurs in "Thread 1". Setting to high as this may affect our tests.
2014-07-31 12:10:55 Alexandros Frantzis description Steps to reproduce: 1. Start app (e.g. calculator) 2. From phablet-shell run 'stop unity8' Expected result: unity8 shuts down properly Actual result: unity8 often (but not always) crashes with a SEGV I have attached thread backtraces of two crash instances. Note that the SEGV site is different in those traces, which indicates that this a race (also reinforced by the fact that the crash doesn't happen always). In both cases the SEGV occurs in "Thread 1". Setting to high as this may affect our tests. Steps to reproduce: 1. Start app (e.g. calculator) 2. From phablet-shell run 'stop unity8' Expected result: unity8 shuts down properly Actual result: unity8 often (but not always) crashes with a SEGV I have attached thread backtraces of two crash instances. Note that the SEGV site is different in those traces, which indicates that this a race (also reinforced by the fact that the crash doesn't happen always). In both cases the SEGV occurs in "Thread 1". Setting to high as this may affect our tests. This occurs on Mako with r161 (haven't tried on other devices).
2014-07-31 13:05:23 Michał Sawicz affects unity8 qtmir
2017-03-13 17:14:49 Michał Sawicz affects qtmir qtmir (Ubuntu)