| Summary: | GMIC causes krita crash | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | thetwo <thetwo222> |
| Component: | G'Mic for Krita | Assignee: | amyspark <amy> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | alvin, amy, halla |
| Priority: | NOR | ||
| Version First Reported In: | 5.0.6 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Other | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
bug
bug |
||
What's PyKrita doing in there...? 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). 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... 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.) Created attachment 148924 [details]
bug
I triggered it twice when testing other things, which seems to be random. Upload the log file here.
|
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.