https://bugs.kde.org/show_bug.cgi?id=452834

            Bug ID: 452834
           Summary: Segmentation fault when closing multiple windows
           Product: krita
           Version: git master (please specify the git hash!)
          Platform: Ubuntu Packages
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: * Unknown
          Assignee: krita-bugs-n...@kde.org
          Reporter: bourumir.wy...@gmail.com
  Target Milestone: ---

Created attachment 148289
  --> https://bugs.kde.org/attachment.cgi?id=148289&action=edit
gdb backtrace

SUMMARY
When more than one window is used, closing windows one by one terminates Krita
with segmentation fault. Segmentation fault message is visible in console and
can be analyzed with gdb. Crash rather than normal termination may prevent
saving state on exit.
***


STEPS TO REPRODUCE
1.  Start krita from the command line, so that the terminal output is visible.
2.  Open one picture.
3.  Open another picture in a new window, using Window -> New Window from menu.
4.  Close both windows, starting from the last opened window. Sometimes the
crash happens when closing the first window, sometimes when another but I have
never seen a clean exit at this point.

At this step Krita will terminate with segmentation fault message in console.
Or, if running under gdb, the following message will appear:

Thread 1 "krita" received signal SIGSEGV, Segmentation fault.
KoToolProxy::priv (this=0x0) at kritadev/krita/libs/flake/KoToolProxy.cpp:495
495         return d;


OBSERVED RESULT
Segmentation fault

EXPECTED RESULT
Normal exit

SOFTWARE/OS VERSIONS
Ubuntu Mate 20.04. 
Standard build as recommended in documentation.
Master branch commit 6419e038185a3377f638d26e34588a56c0f71cd8  .

ADDITIONAL INFORMATION
>From the code analysis looks like the crash happens because 'this' is null in
KisToolProxy::activateToolAction. The bug can be suppressed by adding check if
(this == nullptr) return at the start of this method, but some more in depth
analysis would probably be beneficial, maybe we should not get there starting
from.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to