Inkscape crashing on close with a Segmentation fault. (win64)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
Medium
|
Patrick Storz | ||
Inkscape Devlibs for Windows 64-bit |
New
|
Undecided
|
Unassigned |
Bug Description
Inkscape 0.91pre3 r13670 win64
Windows 7 x64
NOTE: This crash is only noticeable via gdb. Tried the same steps below with the debug on 0.48.5 win32, and it exits correctly without crashing per gdb.
Steps to reproduce:
1. Start out by deleting (or renaming the folder for) your current profile for Inkscape (this proves it's not a profile bug).
2. Start Inkscape so it will create a new profile.
3. Once Inkscape has loaded, close the program.
What should happen:
Inkscape should close 'normally'.
What happens:
Inkscape crashes with a sigsegv.
I've attached the log from gdb to this ticket. Only thing redacted from it is my user account name.
This happens every time you close Inkscape, with or without a profile already present per gdb.
tags: | added: win64 |
Changed in inkscape: | |
status: | Fix Committed → Fix Released |
In the gdb log you can see that the signal is coming from libwinpthread (a POSIX thread library for Windows).
Assuming that winpthread does not have a serious flaw causing this, my assumption is that winpthread is resetting the signal handler for SIGSEGV and using it as a way to control memory access for other threads, not to indicate program fault.