Hi,
another tricky one. I noticed with PCL64 that PI takes a long time to die after I start the program from the debugger and then exit it. Luckily this happens not just when I use my own modules but also when I use DynamicCrop. I didn't try other modules as I was happy to reproduce this with a stock module
This is what the Output window in the debugger shows:
The thread 'Win64 Thread' (0xafc) has exited with code 0 (0x0).
The thread 'Win64 Thread' (0x15e8) has exited with code 0 (0x0).
The thread 'Win64 Thread' (0xca4) has exited with code 0 (0x0).
The thread 'Win64 Thread' (0x1504) has exited with code 0 (0x0).
The thread 'RPC Callback Thread' (0x1440) has exited with code 0 (0x0).
The thread '_threadstartex' (0x458) has exited with code 0 (0x0).
QObject::killTimer: timers cannot be stopped from another thread
QObject::killTimers: timers cannot be stopped from another thread
The thread 'RPC Callback Thread' (0x187c) has exited with code 0 (0x0).
The thread 'Win64 Thread' (0x1968) has exited with code 0 (0x0).
The program '[3568] PixInsight.exe: Native' has exited with code 0 (0x0).
Steps:
- start PI from the VS2008 debugger
- load an image
- do several crop operations with DynamicCrop (I undid each operation, maybe 4 total)
- exit PI
- observe in the debugger that PI stays around for a while
- breaking in the debugger showed it was malloc'ing but that could have been a fluke. This may not be PCL64 related but rather a version thing, I only tried it on this box.
