Comment within <script> element in INX file triggers crash on launch (rev >= 13421)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
Medium
|
jazzynico |
Bug Description
Follow-up report to
- Bug #505920 “inkscape loads extension even if the script specified in <command> doesn't exist”
https:/
Any INX file with a comment within the <script></script> element triggers a crash on launch. Based on tests with archived builds on OS X 10.7.5, this regression was introduced in rev 13421 to fix bug #505920.
Notes:
- it does not matter whether the comment is empty or not
- it does not matter whether scripts referenced via <dependency> are found or not
- it does not matter whether the extension is installed into the shared or into the user's extensions directory.
Steps to reproduce:
1) download attached INX file
2) copy it into ~/.config/
3) try to launch inkscape as usual
Expected result:
Inkscape launches normally, the extension is not loaded since the dependent script is not installed.
Actual result:
Inkscape crashes during parsing of the INX file (AFAIU):
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_
0x00000001003e78ca in Inkscape:
84 _string = _repr->
Related branches
Changed in inkscape: | |
status: | Triaged → In Progress |
Changed in inkscape: | |
status: | Fix Committed → Fix Released |
Backtrace (debug build r13562, OS X 10.7.5)
(Note wrt paths seen in backtrace: for the backtrace Inkscape was launched via shell script which sets custom paths for XDG user locations: e.g. $XDG_CONFIG_HOME is "$HOME/ TEMP/inkmini- quartz" .)