Tweet
Took me a long time to track this problem down, thought I'd add a note in case anyone else runs into the same issue.
I'm running esignal 7.7 on XP, 2.8gig processor, 1gig ram (I had the same problem with esignal 7.6).
With other apps running on the same machine (web browser, etc) after a few hours the menus in esignal would start to disappear. First they are cut off (not displaying the whole menu), and eventually the menus are completely blank and I'd have to kill and restart esignal to recover. At the same time, I was unable to launch any new applications on the machine, even task manager. When I'd try to launch a new app, the hourglass would flash briefly, but no windows would launch. Occasionally, though not every time, esignal would crash. Closing down apps would buy more time with esignal, but eventually a reboot is required to recover and start clean.
In monitoring cpu and memory usage during the problem, I've never seen more than 800meg memory allocated (out of 1gig ram + 3gig swapfile). I've seen the problem with as little as 400meg allocated. cpu use is consistently less than 10%.
The problem turned out to be a desktop heap limitation. XP ships with a default desktop heap of 3072k, which esignal can easily chew through, especially if there are any other apps running on the machine at the same time. I modified heap size to 10240k and have not had any problems since. Tuning desktop heap is described in the following MS knowledge base article:
Hope this helps...
denali
I'm running esignal 7.7 on XP, 2.8gig processor, 1gig ram (I had the same problem with esignal 7.6).
With other apps running on the same machine (web browser, etc) after a few hours the menus in esignal would start to disappear. First they are cut off (not displaying the whole menu), and eventually the menus are completely blank and I'd have to kill and restart esignal to recover. At the same time, I was unable to launch any new applications on the machine, even task manager. When I'd try to launch a new app, the hourglass would flash briefly, but no windows would launch. Occasionally, though not every time, esignal would crash. Closing down apps would buy more time with esignal, but eventually a reboot is required to recover and start clean.
In monitoring cpu and memory usage during the problem, I've never seen more than 800meg memory allocated (out of 1gig ram + 3gig swapfile). I've seen the problem with as little as 400meg allocated. cpu use is consistently less than 10%.
The problem turned out to be a desktop heap limitation. XP ships with a default desktop heap of 3072k, which esignal can easily chew through, especially if there are any other apps running on the machine at the same time. I modified heap size to 10240k and have not had any problems since. Tuning desktop heap is described in the following MS knowledge base article:
Hope this helps...
denali
Comment