Bug 453505 - GMIC causes krita crash
Summary: GMIC causes krita crash
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: G'Mic for Krita (other bugs)
Version First Reported In: 5.0.6
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: amyspark
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-07 13:40 UTC by thetwo
Modified: 2022-05-17 18:14 UTC (History)
3 users (show)

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

Attachments
bug (30.71 KB, text/plain)
2022-05-07 13:40 UTC, thetwo 		Details
bug (26.93 KB, text/plain)
2022-05-17 18:14 UTC, thetwo 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description thetwo 2022-05-07 13:40:08 UTC 
Created attachment 148639 [details]
bug

I first used "Fourier watermark" for the picture.

Then open GMIC again and select "Fourier analysis"

At this point krita crashes. But it only happened once.
Comment 1 amyspark 2022-05-09 09:15:24 UTC 
What's PyKrita doing in there...?
Comment 2 Halla Rempt 2022-05-10 09:54:33 UTC 
I cannot reproduce this. PyKrita probably is in the backtrace because some stuff gets torn down during the crash. (Also, setting Assigned, because you set yourself as assignee).
Comment 3 Alvin Wong 2022-05-10 11:24:18 UTC 
I'm guessing that a Python plugin is used to activate the action that starts the gmic filter, given that `QAction::activate` is in the backtrace...
Comment 4 amyspark 2022-05-16 21:48:49 UTC 
Marking as WORKSFORME because two developers were unable to reproduce the bug.

(I'm using the upcoming G'MIC 3.1.2; feel free to reopen if you face this bug again in the future.)
Comment 5 thetwo 2022-05-17 18:14:28 UTC 
Created attachment 148924 [details]
bug

I triggered it twice when testing other things, which seems to be random. Upload the log file here.