Summary: | Guaranteed crash when opening 2 G'MIC-qt | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Mindaugas <matijunasmindaugas> |
Component: | G'Mic for Krita | Assignee: | amyspark <amy> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | ahab.greybeard, amy, anna.medonosova |
Priority: | NOR | ||
Version: | 4.3.0 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | https://invent.kde.org/graphics/krita/-/commit/ae51edbdf684e858dbb9b42313506dfe256389f2 | Version Fixed In: | |
Attachments: | backtrace of the crash, when first gmic window is closed (3-1); Linux, git master |
Description
Mindaugas
2020-07-21 18:39:37 UTC
To clarify: G'MIC-qt Version is 2.7.1 64bit (what it says at the top). Not the linux version I can confirm this for appimages 4.2.9 to the latest 5.0.0 prealpha. Except that if I apply a filter from the first G'MIC window, it locks up with no crash. Then the operating system reports that it has stopped working and offers to 'Force Quit' or 'Wait'. Force Quit will make krita crash. For the case of opening two G'MIC windows and closing the first one, this is the terminal output: ------------------------------------------------ gmic-qt: socket Key: "{5a5f6e09-9e45-4ea8-845d-deb9fbc25d98}" QObject::startTimer: Timers cannot have negative intervals gmic-qt: socket Key: "{b93c8632-b67b-4f1a-97f7-8b1a7f4ee46b}" QObject::startTimer: Timers cannot have negative intervals QProcess: Destroyed while process ("/opt/krita/gmiclink") is still running. Segmentation fault ---------------------------------------------- Created attachment 130349 [details]
backtrace of the crash, when first gmic window is closed (3-1); Linux, git master
Fixed with the plugin-i-fication of GMic done in https://invent.kde.org/graphics/krita/-/merge_requests/581. |