Thank you for your answer. I'm using the latest version (as stated in the totle of my frst post ) I don't think a docklet is responsible. First, I have no docklet installed except shortcuts, second all the extra threads entry points are withing the objectDock.exe module (well, memory mapped zone anyway: at offset 0x12d40 within the application image). All these threads are waiting for a
Hello, I used ObjectDock (freeware) for a long time now and I noticed that it has trouble when I left it running for some time. After investigating, I found out that it was leaking threads. A lot of them. Leaving the program running for a couple of day would result in 1500+ threads used (only by the O.D. process) and an unresponsivel application. I reported it and never got anything beyond "we'll look at it". So I bought ObjectDock plus yesterday and left i
Stardock Forums
Here is my short list of issues that wheren't reported here (why, oh why do people feel that they should do 20 "Me too" posts...) 1/ I-League way too powerful: I've had many instances of systems leaving for the I-League right after being colonized, before I could have time to resolve the morale issue. Leads the I-League to suck up about 50% of the worlds I colonize in some games when the overall planet's quality is low. 2/ The "rioting" state on system never disapears. I've had