https://bugs.kde.org/show_bug.cgi?id=431561

Harald Sitter <sit...@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
                   |ma/drkonqi/commit/08e204a45 |ma/drkonqi/commit/3ef54a31b
                   |f5dad8bcfdec79740434b36991c |d6a2e440ac563703012864a8e35
                   |020f                        |be4d

--- Comment #5 from Harald Sitter <sit...@kde.org> ---
Git commit 3ef54a31bd6a2e440ac563703012864a8e35be4d by Harald Sitter.
Committed on 22/01/2021 at 14:30.
Pushed by sitter into branch 'Plasma/5.21'.

discard wayland client crashes following compositor crash

when the compositor goes down Qt will abort the clients causing kind of
erroneous crashes that the client can't do anything about. as such we
don't want to allow these reports from going through and instead
shortcut the report dialog to a final conclusion page where we inform
the user about the unfortunate circumstance surrounding this crash.

compositor crash detection is based on a simple check for the relevant
qfatalizing string resulting in a persistent state on the parser


(cherry picked from commit 08e204a45f5dad8bcfdec79740434b36991c020f)

M  +8    -1    src/bugzillaintegration/reportassistantdialog.cpp
M  +25   -0    src/bugzillaintegration/reportassistantpages_base.cpp
M  +18   -0    src/parser/backtraceparser.cpp
M  +6    -0    src/parser/backtraceparser.h
M  +2    -0    src/parser/backtraceparser_p.h
M  +23   -1    src/tests/backtraceparsertest/backtraceparsertest.cpp
M  +3    -0    src/tests/backtraceparsertest/backtraceparsertest.h
M  +5    -0    src/tests/backtraceparsertest/backtraceparsertest_data/data.ini
A  +100  -0   
src/tests/backtraceparsertest/backtraceparsertest_data/test_compositorCrashBug431561

https://invent.kde.org/plasma/drkonqi/commit/3ef54a31bd6a2e440ac563703012864a8e35be4d

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to