Bug 252313 - graphics/spectacle crashes without saving if export to remote storage is attempted
Summary: graphics/spectacle crashes without saving if export to remote storage is atte...
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-kde (Team)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-31 18:40 UTC by Graham Perrin
Modified: 2021-02-22 21:32 UTC (History)
2 users (show)

See Also:
tcberner: maintainer-feedback+


Attachments
Crash handler reports: "The generated crash information is probably not useful" (5.66 KB, text/plain)
2020-12-31 18:40 UTC, Graham Perrin
no flags Details
A screenshot of Spectacle prior to a crash. (199.05 KB, image/png)
2020-12-31 18:41 UTC, Graham Perrin
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Graham Perrin 2020-12-31 18:40:10 UTC
Created attachment 221146 [details]
Crash handler reports: "The generated crash information is probably not useful"

grahamperrin@mowa219-gjp4-8570p:~ % date ; uname -v
Thu 31 Dec 2020 18:39:14 GMT
FreeBSD 13.0-CURRENT #74 r368589: Sun Dec 13 07:55:46 GMT 2020     root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG 
grahamperrin@mowa219-gjp4-8570p:~ % pkg query '%o %v %R' spectacle
graphics/spectacle 20.12.0 FreeBSD
grahamperrin@mowa219-gjp4-8570p:~ % 

----

Operating System: FreeBSD 13.0
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
Kernel Version: 13.0-CURRENT
OS Type: 64-bit
Memory: 15.9 GiB of RAM
Graphics Processor: AMD TURKS
Comment 1 Graham Perrin 2020-12-31 18:41:43 UTC
Created attachment 221148 [details]
A screenshot of Spectacle prior to a crash.
Comment 2 Tobias C. Berner freebsd_committer 2020-12-31 19:17:29 UTC
Moin moin 

I can confirm the crash.


mfg Tobias
Comment 3 Adriaan de Groot freebsd_committer 2021-02-22 15:48:06 UTC
I get a fairly consistent bt like this

```
(lldb) bt
* thread #1, name = 'spectacle', stop reason = signal SIGBUS: hardware error
  * frame #0: 0x000000080246f67f libQt5Core.so.5`QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) + 735
    frame #1: 0x000000080246f287 libQt5Core.so.5`QObject::connectImpl(QObject const*, void**, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) + 295
    frame #2: 0x000000080d9455a2 libKF5kipiplugins.so.5.9.1`KIPIPlugins::KPImagesList::KPImagesList(QWidget*, int) + 3330
    frame #3: 0x000000081908bac3 kipiplugin_remotestorage.so`___lldb_unnamed_symbol106$$kipiplugin_remotestorage.so + 675
    frame #4: 0x0000000819088535 kipiplugin_remotestorage.so`___lldb_unnamed_symbol46$$kipiplugin_remotestorage.so + 101
    frame #5: 0x00000008190880c5 kipiplugin_remotestorage.so`___lldb_unnamed_symbol38$$kipiplugin_remotestorage.so + 293
    frame #6: 0x0000000802472b39 libQt5Core.so.5`___lldb_unnamed_symbol2439$$libQt5Core.so.5 + 1449
    frame #7: 0x0000000801292dfa libQt5Widgets.so.5`QAction::activate(QAction::ActionEvent) + 314
    frame #8: 0x000000080141557d libQt5Widgets.so.5`___lldb_unnamed_symbol1982$$libQt5Widgets.so.5 + 77
    frame #9: 0x0000000801412aab libQt5Widgets.so.5`___lldb_unnamed_symbol1958$$libQt5Widgets.so.5 + 555
    frame #10: 0x0000000801419e60 libQt5Widgets.so.5`QMenu::mouseReleaseEvent(QMouseEvent*) + 704
```

which carries on from where Graham's bt trails off (I think in mouseReleaseEvent). Just seeing that there's dynamic_cast<> in the code makes me think I can guess a reason (there was a similar problem in kleopatra).
Comment 4 Adriaan de Groot freebsd_committer 2021-02-22 21:32:55 UTC
FWIW, I can also trigger the crash consistently with Export to Imageshack, again with a SIGBUS, so I think something **else** is messing up memory.