| Summary: | [wayland] KDevelop crashes when showing/hiding scrollbar text preview | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-ktexteditor | Reporter: | frmdstryr <frmdstryr> |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | christoph, frmdstryr, kdelibs-bugs-null, kossebau, mail |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
frmdstryr
2019-03-12 18:22:19 UTC
I think this is a Qt bug ... Random guess: Try turning off Settings -> Editor -> Appearance -> Borders -> Show text preview on scrollbar. Does that help? Thank you, will try this and update later today. Could you install the debug symbols for KF5' KTextEditor as well, if they aren't yet? Would be also interesting to see what calls exactly here done here: #14 0x00007f5be4a14211 in () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #15 0x00007f5be4a039c1 in () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 Created attachment 118756 [details]
New crash information added by DrKonqi
kdevelop (5.3.2) using Qt 5.12.0
- What I was doing when the application crashed:
@Sven Brauch, disabling the setting appears to work. Thank you very much!
@Friedrich W. H. Kossebau, added the dbgsym
-- Backtrace (Reduced):
#6 0x0000000000000000 in ()
#7 0x00007f298d9506a4 in QWindowPrivate::setVisible(bool) (this=0x556100ef6d10, visible=visible@entry=false) at kernel/qwindow.cpp:402
#8 0x00007f298e6bbd6d in QWidgetWindow::setNativeWindowVisibility(bool) (this=this@entry=0x556111543290, visible=visible@entry=false) at kernel/qwidgetwindow.cpp:205
#9 0x00007f298e69654f in QWidgetPrivate::hide_sys() (this=this@entry=0x5561111eab70) at kernel/qwidget.cpp:8227
#10 0x00007f298e69d900 in QWidgetPrivate::hide_helper() (this=this@entry=0x5561111eab70) at kernel/qwidget.cpp:8155
I'll move this to ktexteditor, then. It's either a bug there or in Qt. Created attachment 118757 [details] New crash information added by DrKonqi kwrite (18.12.3) using Qt 5.12.0 - What I was doing when the application crashed: Thanks. I can reproduce it with KWrite. From looking at the code it looks like there should be a null check in https://github.com/mgerstner/ktexteditor/blob/5a90cee2f73ab80a41220b3dbc67cbe4f0db8d49/src/view/kateviewhelpers.cpp#L466 before delete m_textPreview; This occurs when moving my mouse to another window (one screen to another) in which both the scrollbar leaveEvent and the window deactivated eventFilter will trigger in https://github.com/mgerstner/ktexteditor/blob/5a90cee2f73ab80a41220b3dbc67cbe4f0db8d49/src/view/kateviewhelpers.cpp#L357-L372 -- Backtrace (Reduced): #7 0x00007fdfa35556a4 in QWindowPrivate::setVisible (this=0x55c3f9b63720, visible=visible@entry=false) at kernel/qwindow.cpp:402 #8 0x00007fdfa3dd1d6d in QWidgetWindow::setNativeWindowVisibility (this=this@entry=0x55c3fa498830, visible=visible@entry=false) at kernel/qwidgetwindow.cpp:205 #9 0x00007fdfa3dac54f in QWidgetPrivate::hide_sys (this=this@entry=0x55c3fa42d640) at kernel/qwidget.cpp:8227 #10 0x00007fdfa3db3900 in QWidgetPrivate::hide_helper (this=this@entry=0x55c3fa42d640) at kernel/qwidget.cpp:8155 #11 0x00007fdfa3db85a0 in QWidget::setVisible (this=0x55c3fa3131e0, visible=<optimized out>) at kernel/qwidget.cpp:8357 Also it seems to only occur (on my system) when highlighting is enabled. I guess it takes longer to render or something. Hm, delete on a null pointer is safe though. And the text preview has been in for quite a while now, the issue must be a bit more subtle ... I tried this with current master + Qt 5.13 inside some nested wayland session. Works for me. The pointer is btw. even a QPointer to ensure it is really null if the widget dies. I you can provide some way to reproduce or a new backtrace with more info we could try to take a look again, otherwise I don't know what to fix :( I re-enabled the preview and have not had any of these for two weeks now so I think this can be closed. If it occurs again, I'll create a new issue. Thanks! Thanks for the update; changing status. |