| Summary: | Plasma crash after Laravel throw exception | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Feathers And Down <feathersanddown> |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | plasma-bugs |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.18.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Emoji at taskbar | ||
|
Description
Feathers And Down
2020-08-18 07:58:54 UTC
suddenly appear this in apache error_logs [Tue Aug 18 03:54:55.670218 2020] [php7:notice] [pid 11701] [client 127.0.0.1:43952] PHP Warning: Header may not contain NUL bytes in Unknown on line 0 don't know if related Seems there is no bug here. Currently I was running a faulty kernel from openSUSE Leap 15.2 (5.3.18-lp152.33), reverted to 5.3.18-lp152.26 and I was all day without any issue. Still interesting to know why only plasma crash. ?Thread 8 (Thread 0x7f6d9dc6c700 (LWP 12006)): [KCrash Handler] #4 std::__atomic_base<int>::operator++ (this=0x15bd) at /usr/include/c++/7/bits/atomic_base.h:296 #5 QAtomicOps<int>::ref<int> (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:265 #6 QBasicAtomicInteger<int>::ref (this=0x15bd) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:114 #7 QRawFontPrivate::setFontEngine (engine=0x15b1, this=0x7f6d9818a900) at text/qrawfont_p.h:128 #8 glyphRunWithInfo (fontEngine=0x15b1, glyphLayout=..., pos=..., flags=..., selectionX=..., selectionWidth=..., glyphsStart=0, glyphsEnd=0, logClusters=<optimized out>, textPosition=0, textLength=35) at text/qtextlayout.cpp:2230 #9 0x00007f6df70b9250 in QTextLine::glyphRuns (this=this@entry=0x7f6d9dc694d0, from=from@entry=0, length=<optimized out>) at text/qtextlayout.cpp:2413 #10 0x00007f6dfa8ec81c in QQuickTextNodeEngine::addGlyphsInRange (this=this@entry=0x7f6d9dc69470, rangeStart=rangeStart@entry=0, rangeLength=rangeLength@entry=35, color=..., backgroundColor=..., selectionStart=selectionStart@entry=-1, selectionEnd=-1) at /usr/src/debug/libqt5-qtdeclarative-5.12.7-lp152.2.2.x86_64/src/quick/items/qquicktextnodeengine.cpp:593 #11 0x00007f6dfa8ecda7 in QQuickTextNodeEngine::addGlyphsForRanges (this=this@entry=0x7f6d9dc69470, ranges=..., start=start@entry=0, end=35, selectionStart=selectionStart@entry=-1, selectionEnd=selectionEnd@entry=-1) at /usr/src/debug/libqt5-qtdeclarative-5.12.7-lp152.2.2.x86_64/src/quick/items/qquicktextnodeengine.cpp:565 We have a known crash in Qt if rendering a QQuickText item with an emoji/UTF-8 in it, from the trace it's similar. Oh, thanks for reply. I've commented this: https://bugs.kde.org/show_bug.cgi?id=425483#c2 related to a buggy (for me) kernel version. Currently I got same issue with a previous 5.3.18-lp152.26. So if is an emoji the culprit.... Is there a way to mitigate? my all day opensuse work station stuck my job :-(. Thanks in advance. Created attachment 131026 [details]
Emoji at taskbar
Emoji at task bar beside favicon
Just to add: if you say "emoji" related problem, should be something like this: https://bugs.kde.org/attachment.cgi?id=131026 ? Seems is where point your advice. Thanks in advance After lasts zypper dup on my opensuse Leap 15.2 i didn't had this issue again, seems fixed in any of those patches. Hope someone else can say something on this to close this report. The backtrace indicates a crash in QQuick glyph handling. If you can reproduce, please report this issue to Qt developers via https://bugreports.qt.io/ |