Jon,

Don't know if I can help you debug this one, but DF locked up, leaving non-responsive buttons all over the screen. Looking at the log, DF was getting the clicks but couldn't do anything because of an out-of-memory condition. Unfortunately, the log doesn't go back far enough - log truncation can be annoying. See a snippet below. I keep my XP system running for months without shutting down. Perhaps you might want to keep track of repeating FAIL notices and report them on (1) an hourly basis and (2) when you detect user interaction to prevent losing clarity in the log.

I had to use task manager's End Task. Don't know if that causes a dump or something you could use. DF started up and is running fine now.

2010/10/26 11:09:12.54: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:09:16.93: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:09:21.96: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:09:30.54: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:09:36.42: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:09:40.10: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:09:53.40: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:09:57.54: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:10:07.06: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:10:08.95: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:10:18.38: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:10:18.38: INFO: HookFormProcess:WndProc: Ignoring double left-click: 0.000s
2010/10/26 11:10:18.38: INFO: HookFormProcess:WndProc: Ignoring double left-click: 0.000s
2010/10/26 11:10:20.95: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:10:28.43: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:10:28.43: INFO: HookFormProcess:WndProc: Ignoring double left-click: 0.000s
2010/10/26 11:10:28.43: INFO: HookFormProcess:WndProc: Ignoring double left-click: 0.000s
2010/10/26 11:10:31.54: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:10:40.62: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:10:40.62: INFO: HookFormProcess:WndProc: Ignoring double left-click: 0.000s
2010/10/26 11:10:40.63: INFO: HookFormProcess:WndProc: Ignoring double left-click: 0.016s
2010/10/26 11:10:44.99: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:10:47.77: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:10:51.09: FAIL: TaskManager:AddTaskPrivate: Exception of type 'System.OutOfMemoryException' was thrown.
2010/10/26 11:11:28.04: INFO: ---------------------------------------------------------------------

I don't know how to repro. The machine is on for months. I returned after the week end and DF was locked up. Hope you can keep track of repeating errors so they don't fill the log. If it happens again, sure, I'll check in!

Just after I posted, I noticed it locked up again. Attached is an excerpt from the log that shows before and middle. DF is hung in this instance and I will leave it that way until you give me further instructions (to get a dump or other diagnostic).

Here's the thing... I am debugging a native application with an ActiveX control that doesn't seem to be freeing resources (not my ActiveX control, btw). It had just gotten a protection exception and I had to kill the program from the IDE. As a native app, I don't think it is doing anything other than using up system memory. It isn't dot net. That's my best info I can give you at this point. So take a look at the log and get back to me.

Will do. Tomorrow, I'll try to lock up my product and see if it locks up yours...

Can't repro. Apparently, I fixed my product so it doesn't hog memory the same way.

I suggest using a tool to lower the memory on your system to see if you can get it to happen for you. Otherwise, if it should happen again, I'll see what I can get to you.