Bug 399282 - Random freezes when capturing an area running multiple gpu's
Summary: Random freezes when capturing an area running multiple gpu's
Status: RESOLVED WORKSFORME
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 18.04.2
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-01 15:36 UTC by qlum
Modified: 2022-11-11 05:20 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description qlum 2018-10-01 15:36:54 UTC
SUMMARY
Random system freeze when capturing area

STEPS TO REPRODUCE
1. Set capture mode to rectangular region
2. click take a new screenshot
3. select and area
4. repeat until the system freezes 

OBSERVED RESULT
I can still move my cursor but the keyboard is completely unresponsive and the screen is stuck on the area selection interface. (completely unresponsive as in even toggling numlock does nothing)


SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.49
Qt Version: 5.11.1

ADDITIONAL INFORMATION
The problem arises only when I have both my igp and gpu enabled at the same time (needed to handle my 5 monitors at the same time)
The igp is from a kaby lake i5
the gpu is a r7 250 running the default open source drivers

When just running on the gpu the problem does not occur and the area selection is also generally laggy when having all my monitors connected. which is otherwise not the case.

If you need any other information, just let me know.
Comment 1 Julian Steinmann 2019-03-02 14:16:37 UTC
Can you still reproduce this problem? Sadly only a few people have a multi-GPU setup, so it's quite hard to test & reproduce this problem for us.
Comment 2 qlum 2019-03-08 16:59:10 UTC
Sadly I can still reproduce the issue. Sorry for the late response it happens on my machine at work and didn't have an opportunity to verify earlier. It does however seem pretty hard to reproduce at times. 

Another thing is that the selection is quite laggy where on a single gpu it is not.
Comment 3 Christoph Feck 2019-03-15 23:17:27 UTC
Thanks for the update; changing status.
Comment 4 Erik 2020-06-19 10:04:23 UTC
Mager bug Debian 10 KDE
Freezes when taking area shut can't press enter
only option to restart pc or kill spectacle

ctrl+alt+f1 //start terminal
htop //start htop
kill spectacle
ctrl+alt+f7 //back to desktop
Comment 5 Ilpo Kantonen 2020-06-19 12:01:17 UTC
I use Kubuntu 18.04. If I have two spectacle screenshot running that freezes whole KDE or Kubuntu. I think that I have not remembered I have already spectacle running when I decide to take a new screen shot and then I start new spectacle. Or it duplicates itself running instances when I take several screenshots.

It can be avoided if spectacle is singleton. Or there is something which uses same crirical resources of system and freezes.

Spectacle version is 17.12.3.

Maybe this is same bug or new bug.
Comment 6 Justin Zobel 2022-10-12 03:49:54 UTC
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!
Comment 7 qlum 2022-10-12 16:02:55 UTC
I can no longer reproduce the issue, even forgot I opened it.
I can't exactly pinpoint when it resolved itself, but I am no longer having this issue.
Comment 8 Ilpo Kantonen 2022-10-12 20:02:24 UTC
I remember that.  That happened, because there were more than one Spectacle windows open in same time. It has not happened anymore since the new program version came out. Thanks!
Comment 9 Bug Janitor Service 2022-10-27 05:03:33 UTC
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!
Comment 10 Bug Janitor Service 2022-11-11 05:20:15 UTC
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!