Troubleshooting requests Thread last updated on 2003-05-21 09:52:48

Posted by member 1316 on 2003-05-20 13:52:48

I haven't seen requests for this stuff yet, but I may have missed them. Anyways, I think it would be a great idea to have a special utility that would allow you to view the currently running LS modules, and see their CPU usage, RAM usage, etc. This would be great if you're having problems with "LiteStep" locking up, but you have no idea which module is actually freezing. And in the same utility, the ability to end module processes, and to start new processes.

Posted by member 99 on 2003-05-20 17:53:33 link

I have a really ugly and unconfigurable module that will track rough CPU usage per module, memory and resource usage should be possible, but more difficult.

LiteStep modules are not actually in their own processes, so Windows doesn't make this easy.

Posted by member 503 on 2003-05-20 19:11:12 link

Wow, Rabid, how'd you do that?

Posted by member 35 on 2003-05-20 19:29:19 link

Rabid ure my hero!

Posted by member 31 on 2003-05-20 21:07:51 link

I'd be interseted in knowing the 'how' of it as well :)

Posted by member 99 on 2003-05-20 21:34:16 link

The key word is *rough*. It hooks the wndproc of every litestep window, then keeps track of how long the module takes to respond to each message. There are a good number of things that will make it crash or report incorrect information.

And I haven't released it because right now it puts this information in an unconfigurable white box at a fixed location. It was basically a proof-of-concept, then I wanted to make it use whatever evolved from skinbox, which I haven't finished yet. :/

Posted by member 1316 on 2003-05-21 09:52:48 link

Well, I can be patient. It's just something I thought of a while ago, but kept forgetting to mention. If I had any programming skillz myself, I would attempt it, but I don't, so I haven't. I'm JUST good enough to modify the litestep configs.