PDA

View Full Version : Memory leaks in MultiTouch utilities

Tigger
11-06-2003, 02:26 PM
I've started leaving the MultiTouch Utilities start bar and MyGesture Editor running because I find it much easier to find gestures in the editor than in the quick reference pages. Over the last couple of days, I've had problems with my Windows system that appear to be caused by memory or resource leaks in the FingerWorks utilities.

Yesterday, my system started behaving like one of the running programs was stuck in a tight loop. I suspected the editor, but things were behaving so badly, I had to log off my ID in order to get all the programs to be closed.

Today, I started getting a low virtual memory message popped up by Windows. Sure enough, when I brought up the task manager, the editor had a ton of memory allocated. I used the task manager to kill it, and my memory usage dropped back down into the normal range.

So, I think that there is a memory leak in the Gesture Editor and possibly in the utilities start bar.

Sorry to be the bearer of bad news,
Danny
fingerworks
11-06-2003, 04:10 PM
How much do you consider a ton? Because it's a complex application implemented in Java, the gesture editor is naturally a bit of a memory hog. The utilities launchbar alone draws 20MByte, and by the time you launch the gesture editor it may draw 40-45MByte.

So you're saying more than 45 Mbyte, right?
Tigger
11-06-2003, 06:48 PM
I'll have to try to recreate and pay attention to the numbers. The numbers were significantly more than anything else I had running, but they may be in line with the numbers you're quoting.

I had the launch bar, gesture editor and my my typical applications running which consists primarily of SlickEdit, Lotus Notes, several instances of IE and a bunch of command prompts. Without the FingerWorks apps, I can usually leave the other apps up for days at a time with no problems. When I added the FingerWorks apps into the mix, I started getting the virtual memory low messages. Maybe they're just enough to push me over the edge so that I need to increase my paging space. If I recreate the problem, I'll report the numbers.