Summary: | Crash In QScreen::geometry | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | frmdstryr <frmdstryr> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | a.saoutkin, frmdstryr, jgrulich, sommerluk |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.5.0 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi Menu's popup at wrong location New crash information added by DrKonqi New crash information added by DrKonqi qtdiag output New crash information added by DrKonqi |
Description
frmdstryr
2020-02-04 15:41:41 UTC
Created attachment 125666 [details]
New crash information added by DrKonqi
kdevelop (5.5.0) using Qt 5.13.2
- What I was doing when the application crashed:
As soon as I scroll in a file it crashes. It was working fine before updating today.
-- Backtrace (Reduced):
#6 0x00007feeec408780 in QScreen::geometry() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#7 0x00007feeee332c42 in () at /usr/lib/x86_64-linux-gnu/libKDevPlatformUtil.so.55
#8 0x00007feeeb951362 in QObject::event(QEvent*) (this=0x7feeee54ed70, e=<optimized out>) at kernel/qobject.cpp:1260
#9 0x00007feeed104eac in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55cc9c959e80, receiver=receiver@entry=0x7feeee54ed70, e=e@entry=0x55cc9e6b54e0) at kernel/qapplication.cpp:3703
#10 0x00007feeed10c4b0 in QApplication::notify(QObject*, QEvent*) (this=0x7ffd4f4d4480, receiver=0x7feeee54ed70, e=0x55cc9e6b54e0) at kernel/qapplication.cpp:3449
Created attachment 125668 [details]
New crash information added by DrKonqi
kdevelop (5.5.0) using Qt 5.13.2
- What I was doing when the application crashed:
I restarted and tried to use my project again. Have to stick with KWrite for now...
-- Backtrace (Reduced):
#6 0x00007f8b39616780 in QScreen::geometry() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#7 0x00007f8b3b540c42 in () at /usr/lib/x86_64-linux-gnu/libKDevPlatformUtil.so.55
#8 0x00007f8b38b5f362 in QObject::event(QEvent*) (this=0x7f8b3b75cd70, e=<optimized out>) at kernel/qobject.cpp:1260
#9 0x00007f8b3a312eac in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55ba56b52e80, receiver=receiver@entry=0x7f8b3b75cd70, e=e@entry=0x55ba584ba130) at kernel/qapplication.cpp:3703
#10 0x00007f8b3a31a4b0 in QApplication::notify(QObject*, QEvent*) (this=0x7ffec94ba180, receiver=0x7f8b3b75cd70, e=0x55ba584ba130) at kernel/qapplication.cpp:3449
That's an odd one. Could you install debug symbols please? I wonder if it's ActiveTooltip that fails for you, i.e. line 109 in activetooltip.cpp: QRect screenGeometry = QGuiApplication::screenAt(fullGeometry.topLeft())->geometry(); if we fail to find a screen for the geometry that could crash. But... Why would we fail to find a screen - maybe the geometry is fubared? Do you have a special multi-screen layout? Hidpi? Created attachment 125674 [details]
Menu's popup at wrong location
It's a laptop with a 4k screen running at 2x scale. There were no displays connected. I'll try again with debug symbols. The context menu's popup at the wrong location as well in KDevelop but work fine in Kate / KWrite (see attached picture). Created attachment 125675 [details]
New crash information added by DrKonqi
kdevelop (5.5.0) using Qt 5.13.2
- What I was doing when the application crashed:
Re-opened project. It seems to occur when it tries to popup info on one of the code items.
-- Backtrace (Reduced):
#6 0x00007fc39221d780 in QScreen::geometry() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#7 0x00007fc394147c42 in () at /usr/lib/x86_64-linux-gnu/libKDevPlatformUtil.so.55
#8 0x00007fc391766362 in QObject::event(QEvent*) (this=0x7fc394363d70, e=<optimized out>) at kernel/qobject.cpp:1260
#9 0x00007fc392f19eac in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x56245f00be80, receiver=receiver@entry=0x7fc394363d70, e=e@entry=0x56247c4bae10) at kernel/qapplication.cpp:3703
#10 0x00007fc392f214b0 in QApplication::notify(QObject*, QEvent*) (this=0x7fff54bb2d20, receiver=0x7fc394363d70, e=0x56247c4bae10) at kernel/qapplication.cpp:3449
This does not occur on another project that doesn't have code hinting popups so it does seem to be related to the popup info/hints. Also the messed up menu's also occur on the "terminal" app so it's not specific to KDevelop. quite probably this is a 4K issue then, can you try to see if it reproduces when you set the scale factor to 1? Obviously it will look like crap, but I want to see if that fixes the issue for you or not. And again, if at all possible, please install debug symbols for kdevelop, they are still missing, see: #7 0x00007fc394147c42 in () at /usr/lib/x86_64-linux-gnu/libKDevPlatformUtil.so.55 Created attachment 125717 [details]
New crash information added by DrKonqi
kdevelop (5.5.0) using Qt 5.13.2
- What I was doing when the application crashed:
Sorry I had kdevelop-dbgsym but not the kdevplatform55-libs-dbgsym.
This is with 2x scaling, will try again without scaling.
-- Backtrace (Reduced):
#6 0x00007f047e5f0780 in QScreen::geometry() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#7 0x00007f048051ac42 in (anonymous namespace)::ActiveToolTipManager::doVisibility() (this=0x7f0480736d70 <(anonymous namespace)::manager()::m>) at ./kdevplatform/util/activetooltip.cpp:109
#8 0x00007f047db39362 in QObject::event(QEvent*) (this=0x7f0480736d70 <(anonymous namespace)::manager()::m>, e=<optimized out>) at kernel/qobject.cpp:1260
#9 0x00007f047f2eceac in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x557209099e80, receiver=receiver@entry=0x7f0480736d70 <(anonymous namespace)::manager()::m>, e=e@entry=0x55720b0ccc50) at kernel/qapplication.cpp:3703
#10 0x00007f047f2f44b0 in QApplication::notify(QObject*, QEvent*) (this=0x7ffd87cf1aa0, receiver=0x7f0480736d70 <(anonymous namespace)::manager()::m>, e=0x55720b0ccc50) at kernel/qapplication.cpp:3449
When I change the scaling to 1.0 and the menu's show up at the correct location as well and I can't get it to crash. Thank you, that makes it very clear where it crashes. What's unfortunate is that I cannot reproduce this. I talked to Aleix yesterday and was even running KDevelop on a 4k + 2x configuration and didn't see any such issues either. So, that leaves me a bit blindfolded as to the question on how to fix this properly... Could you please paste me the output of `qtdiag` that corresponds to your screen(s)? E.g. on my non-hidpi laptop this section looks like this: ``` Screens: 1, High DPI scaling: inactive # 0 "eDP-1" Depth: 24 Primary: yes Manufacturer: LGD Model: Serial number: Geometry: 1920x1080+0+0 Available: 1920x1044+0+0 Physical size: 309x174 mm Refresh: 60.0204 Hz Power state: 0 Physical DPI: 157.825,157.655 Logical DPI: 96,96.2526 Subpixel_None DevicePixelRatio: 1 Pixel density: 1 Primary orientation: 2 Orientation: 2 Native orientation: 0 OrientationUpdateMask: 0 ``` Or, better yet, are you able to compile KDevelop from sources? Then I could fire of some patches in your direction to test things out? For now, I'll just prevent the crash - that's easy. But this will come at the cost of essentially disabling the tooltips altogether then :( Git commit e37549a4b04cd88174b968b37c7061376e0c6744 by Milian Wolff. Committed on 07/02/2020 at 11:40. Pushed by mwolff into branch 'master'. Don't crash when we fail to find a screen for the active tooltip There's a hidden hidpi issue lurking in this code base. What's odd is that it's not easily reproducible everywhere. For now, prevent a crash when we fail to find a screen at the tooltip's location. M +6 -1 kdevplatform/util/activetooltip.cpp https://invent.kde.org/kde/kdevelop/commit/e37549a4b04cd88174b968b37c7061376e0c6744 Created attachment 125826 [details]
qtdiag output
Attached the qtdiag output.
At my office I normally have two monitors attached, A regular 1920x1080 monitor and 4k monitor. So there's three screens FHD, 4k laptop at 2x scale, and 4k monitor (which I run at 2560 x 1440).
Strangely this only happens when the monitors are _not_ plugged in, maybe it's something leftover from that configuration that does not reset with a restart?
quite odd, that output looks super harmless - I think we can't do much more about this bug until a developer can reproduce it and debug it... at least it shouldn't crash anymore (I hope) Git commit aa7bc707be21ac268a380a6b4ad972f62b3a72df by Milian Wolff. Committed on 14/02/2020 at 10:03. Pushed by mwolff into branch '5.5'. Don't crash when we fail to find a screen for the active tooltip There's a hidden hidpi issue lurking in this code base. What's odd is that it's not easily reproducible everywhere. For now, prevent a crash when we fail to find a screen at the tooltip's location. (cherry picked from commit e37549a4b04cd88174b968b37c7061376e0c6744) M +6 -1 kdevplatform/util/activetooltip.cpp https://invent.kde.org/kde/kdevelop/commit/aa7bc707be21ac268a380a6b4ad972f62b3a72df *** Bug 417149 has been marked as a duplicate of this bug. *** Created attachment 129120 [details]
New crash information added by DrKonqi
kdevelop (5.5.0) using Qt 5.12.8
Hit the same issue with hovering for a pop-up. Have two monitors (900x1440) and (1920x1080). crashed happened whilst KDevelop was open in the alter
-- Backtrace (Reduced):
#6 0x00007fd91eb2c154 in QScreen::geometry() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#7 0x00007fd91fcd6cc9 in () at /usr/lib/x86_64-linux-gnu/libKDevPlatformUtil.so.55
[...]
#9 0x00007fd91fcd2a58 in KDevelop::ActiveToolTip::resizeEvent(QResizeEvent*) () at /usr/lib/x86_64-linux-gnu/libKDevPlatformUtil.so.55
#10 0x00007fd91f284947 in QWidget::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007fd91f241a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
*** Bug 426419 has been marked as a duplicate of this bug. *** Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |