Comment 12 for bug 1655619
Revision history for this message
| Patrick Storz (ede123) wrote Re: Inkscape 0.92 CPU Usage Higher than 0.91 | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
Hmm... this issue is really strange (read: might not even be related to .pyc files in the way I thought). For example Scour always works fine for me and it certainly uses modules.
Some things I noticed:
- One similarity between the two conflicting extensions is that they both try to spawn a new instance of Inkscape via "Popen", though.
- I tried to execute the command in question and at least when executed manually on the command line it doesn't fail.
- However it's obvious that at some point the spawned subprocess is locking up: If you look in task manager you'll find your original inkscape.exe (0% CPU) the spawned inkscape.com (0% CPU) and it's own inkscape.exe (100% of one core).
Question is: What is the spawned instance of Inkscape doing, and why is it locking up?