Comment 12 for bug 1659172

The actual child process thread that is eating cpu will close every time I open properties to the threads tab, so I'm getting nothing from it. But I can see that there are 10 associated threads in the handles view before attempting to open the properties. I've attached a screenshot of the "Environment" tab (same for parent and child process shown in Process Explorer tree view).

From the "parent" inkscape thread properties (obviously the thread # changes every time, but the stacks are the same):

Stack for thread 15860: (inkscape.com+0x1500) [State: Wait:UserRequest]
ntdll.dll!NtWaitForSingleObject+0x14
KERNELBASE.dll!WaitForSingleObjectEx+0x8f
inkscape.com+0x30c3
inkscape.com+0x13e8
inkscape.com+0x151b
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21

Stack for thread 20748: (inkscape.com+0x15b0) [State: Wait:Executive]
Stack for thread 17180: (inkscape.com+0x15b0) [State: Wait:Executive]
Stack for thread 14988: (inkscape.com+0x15b0) [State: Wait:Executive]
 (all three have same stack)
ntdll.dll!ZwReadFile+0x14
KERNELBASE.dll!ReadFile+0x74
inkscape.com+0x1608
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21

Stack for thread 20116: (ntdll.dll!RtlReleaseSRWLockExclusive+0x1370) [State: Wait:WrQueue]
  (This one sometimes goes away while inkscape continues to run)
ntdll.dll!NtWaitForWorkViaWorkerFactory+0x14
ntdll.dll!RtlReleaseSRWLockExclusive+0x1ade
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21