Running CodeWarrior with Windowblinds causes CW to leak memory

Looking for a solution without having to unload WB

from WinCustomize Forums
When I run Metrowerks CodeWarrior for PalmOS (a development environment for developing Palm Apps), my PC quickly runs out of memory if WB is running. This happens even if I completely disable CodeWarrior in the WB app specific settings. The only way I can get CodeWarrior to run normally, and not eat up all of my memory in minutes, is to completely unload WB. However, I can leave all of my other Object Desktop apps running. Currently that's ObjectDock Plus, some DX widgets, CursorXP, Enhanced Dialog and RightClick.

I really hate unloading WB ( Windows is just plain Ugly without my WB themes! ). I just wish there was some way I could get the two apps to co-exist.

I'd be very grateful for a solution, or even just a suggestion of something I could try, to hopefully solve this problem.

Thanks!
-mike

Edit: I edited the title so that it more accurately describes the actual problem
windowblinds
4,023 views 5 replies
Reply #1 from Stardock Forums Top
What precisely is using up the memory? Which process?
Reply #2 from WinCustomize Forums Top
What precisely is using up the memory? Which process?


It's CodeWarrior that's using up memory. I've watched it with Task Manager. If WindowBlinds is not running the CodeWarrior stays at about 20,000-22,000k. If WindowBlinds is runing, then the CodeWarrior process (called IDE.exe) quickly jumps 100,000k and then 200,000k and keeps climbing. The weird thing is that if I don't open any windows and just make changes to the resources (move around controls on various windows or even add new controls or new windows) and then recompile without opening any .cpp or .h files, then it accumulates memory much more slowly. But, as soon as I start opening windows to make coding changes, it just runs away like crazy. If I unload WB while CW is running, it doesn't let go of the memory automatically. I have to shutdown CW, unload WB and then restart CW. Basically, if WB is not running when I start CW, then everything is ok.

I just tried an experiment. With CW running I loaded WB and watched the memory use of IDE.exe. It immediately jumped from 21,000k to about 45,000k. Then I opened a couple .cpp and .h files and watched the memory increase by 2-3,000k for each file I open. I see the memory increase even when I close a file. Each window I close causes the memory to increase by about 1,000k. The memory is never freed until I shutdown CW.

Let me know if there are any other tests I could try that might shed light on the cause of the problem. Or maybe the problem is with Metrowerks CW. I understand that this is quite likely, but I don't think it will be very likely that Metrowerks will be inclined to fix it.

Thanks!
Offworld Trading Company
Reply #3 from Stardock Forums Top
Have you tried excluding it?
Reply #4 from WinCustomize Forums Top
Yes, that was the first thing I tried. I said this in my initial post but didn't get the terminology correct I guess. What I said was:

This happens even if I completely disable CodeWarrior in the WB app specific settings.

What I meant was that it happens even if I exclude it. In fact, it was excluded when I did the test I describe in my previous post where memory would be used when opening or closing source code windows.

Thanks for your help with this, I really do hope there is something that can be done. I can unload WB, but like I said I really hate to do that now that I've gotten so used to it. I'm currently developing a Palm App with CodeWarrior so unfortunately I have to unload WB almost all the time now.
Reply #5 from WinCustomize Forums Top
This happens even if I completely disable CodeWarrior in the WB app specific settings.