command line sometimes freezes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I am using a script to use Inkscape 0.92 via command line (indirectly) in Windows 10.
I've found that after running the script, Inkscape will sometimes not close properly leaving an instance running in the background eating up to 12-18% of cpu (quad core/8 threads) while not visibly doing anything: It completes it's tasks every time as far as I can tell, as the script keeps running, returns correct results and properly saves/converts the files requested. This started happening after updating to 0.92 (I believe I had 0.91 before and never noticed this problem then). I first noticed this when my computer was bogged down and opening task manager, I found 8+ instances of inkscape running in the background. Since then when running my scripts I keep task manager open to kill it on the random times when it doesn't close properly (or I listen for when my cpu fan jumps level, indicating inkscape didn't close).
I run the following commands
"C:\Program Files\Inkscape\
(returning Inkscape 0.92.0 r15299)
and
"C:\Program Files\Inkscape\
The second command is usually used in a loop and runs 1-8 times. Sometimes it gets through everything without any problems, and sometimes I'll find 3 instances weren't closed.
Just now running
"C:\Program Files\Inkscape\
directly in the command line (not in the scripting software) did the same thing: It would frequently leave Inkscape open and not return, even though it gave the correct version. Sometimes it would close.
Thanks for taking the time to file a report!
Does it happen with some specific SVG files? If so, could you please attach a copy so that we can investigate?