| Summary: | Discover crashes on every start using git snapshots | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Robby Engelmann <robby.engelmann> |
| Component: | discover | Assignee: | Dan Leinir Turthra Jensen <leinir> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | crash | CC: | aleixpol, fabian, lbeltrame, robby.engelmann |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
QML cache Discover |
||
|
Description
Robby Engelmann
2021-07-20 18:15:08 UTC
Created attachment 140406 [details]
New crash information added by DrKonqi
plasma-discover (5.22.80) using Qt 5.15.2
- What I was doing when the application crashed:
Just starting Discover. No matter whether to start via konsole, or Application Launcher.
Also ELISA and System Monitor crashes directly upon start
-- Backtrace (Reduced):
#4 QQmlRefPointer<QQmlTypePrivate const>::QQmlRefPointer(QQmlRefPointer<QQmlTypePrivate const> const&) (other=..., this=0x7f52c16f5750, this@entry=0x7f52c16f56d0) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/qml/ftw/qqmlrefcount_p.h:152
#5 QQmlType::QQmlType(QQmlType const&) (this=this@entry=0x7f52c16f5750) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmltype.cpp:121
#6 0x00007f52d196b74c in QQmlPropertyCacheCreator<QQmlTypeCompiler>::propertyCacheForObject(QmlIR::Object const*, QQmlBindingInstantiationContext const&, QQmlError*) const (this=this@entry=0x7f52c16f5ad0, obj=obj@entry=0x7f52b019fb08, context=..., error=error@entry=0x7f52c16f57e8) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:310
#7 0x00007f52d196e341 in QQmlPropertyCacheCreator<QQmlTypeCompiler>::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&, QQmlPropertyCacheCreator<QQmlTypeCompiler>::VMEMetaObjectIsRequired) (this=this@entry=0x7f52c16f5ad0, objectIndex=3, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator<QQmlTypeCompiler>::VMEMetaObjectIsRequired::Maybe) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:264
#8 0x00007f52d196e6cc in QQmlPropertyCacheCreator<QQmlTypeCompiler>::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&, QQmlPropertyCacheCreator<QQmlTypeCompiler>::VMEMetaObjectIsRequired) (this=this@entry=0x7f52c16f5ad0, objectIndex=objectIndex@entry=0, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator<QQmlTypeCompiler>::VMEMetaObjectIsRequired::Maybe) at /usr/include/qt5/QtCore/qendian.h:290
Can it be that there's a problem with the builds there? It's crashing right in QML and I do not recognize the backtrace. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! I do not know about this, sorry. Try removing the QML cache: ~/.cache/<app name>/qmlcache Or rather, move it away. Don't delete it. Removing the QML cache: ~/.cache/<app name>/qmlcache indeed helped here for Discover and Elisa (here same issue). What do you think was happening here? It's been a longstanding bug I've been experiencing (often with Mesa updates) in which the QML compiled cache is somehow not compatible and causes crashes. I hope you kept the files, so that at last it can be diagnosed somehow (I'm still not sure it's a Qt bug or a bug elsewhere). F***, I already removed them :-(, but I can keep an eye on this, I regularly had this issue here. It was solved some time ago and reappeared quite soon. Either way, this is not a bug in Discover per se, so let's close this. The issue appeared again. This time I save the qml cache of discover (attached here) Created attachment 142668 [details]
QML cache Discover
(In reply to Luca Beltrame from comment #10) > Either way, this is not a bug in Discover per se, so let's close this. I re-opened, added the qmlcache missing last time for you. Feel free to close again after you saw it. Let's close this - this is a downstream issue. I currently don't have the link to the bug report, but the summary is that SOURCE_DATE_EPOCH is set based on the (human written) changelog only, and not updated on git builds. So the qmlcache appears to have a valid timestamp still. This needs to be fixed to take other sources into account as well. |