Bug 455277 - No screenshot taken and memory leak when using keyboard shortcut twice
Summary: No screenshot taken and memory leak when using keyboard shortcut twice
Status: RESOLVED NOT A BUG
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Manjaro Linux
: NOR major
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-14 20:42 UTC by Antonio Prcela
Modified: 2022-06-16 13:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Antonio Prcela 2022-06-14 20:42:21 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. launch Spectacle 22.07.70 with any keyboard shortcut
2. no screenshot taken, process `spectacle` visible and running 
3. hit the same kb shortcut again, this time the screenshot gets taken
4. wait for the notification to disappear
5. spectacle eats up all the RAM

bonus: 
1. hit meta+shift+print for rectangular region
2. choose region, press enter or double click
3. no screenshot, so hit meta+shift+print again
4. can't confirm rectangular region , neither cancel with Esc
5. switch to another tty, ctrl+alt+F2, kill spectacle process

OBSERVED RESULT
spectacle runs in background and on second shortcut press, eats RAM

EXPECTED RESULT
should take the appropriate screenshot according to the shortcuts pressed

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
Kernel Version: 5.18.3-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 15,4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

ADDITIONAL INFORMATION
spectacle 22.07.70 (current master branch with last commit e410c573)

Setting now as major, need someone to either confirm or deny this behavior.
Comment 1 Antonio Prcela 2022-06-16 13:25:03 UTC
Sorry, had to delete both build and usr folder in my kde folder, rebuild spectacle with `kdesrc-build spectacle`. Now it works poperly