CF application freezes PDA completely

[Guest]

We have an application developed in dotnet CF which, if run for some days, completely freezes the PDA. We can't even turn off the power by pressing the power button, the only resort is to soft reset it
The application which is a portable remotecontrol to a external system, consists of two main threads. One for command delegation between a communication class and the GUI, and one for checking if the wlan is connected or disconnected. We use several unmanged calls to enable complete control of all the buttons(the power button is not mapped) and also unmanged calls to a iPAQ specific API which provides information about the wlan(IPAQUTILWLAN.dll)
Since the problem only ocurs if the aplication is run non stop for several days, my suspesion is that it could be a memory leak.
Does anybody have an idea what this problem could be caused by? How can I debug this problem more specificaly by for example getting memory usage and other low level information. I've tried logging severel informations from within the program(thread loop count, wlan requests, and other info) but this is not enough though

Thanks in advance

 

[Isaias Formacio Serna]

I'm not sure on this one but I think I had the same problem before, the
thing is that you cannot modify the GUI from an external thread other than
the main thread, if you try to do it, the application usually freezes... So,
if you're going to modify the GUI you might want to try the Invoke method.

I hope it helps,

Isaias Formacio

We have an application developed in dotnet CF which, if run for some days,

completely freezes the PDA. We can't even turn off the power by pressing the
power button, the only resort is to soft reset it.

The application which is a portable remotecontrol to a external system,

consists of two main threads. One for command delegation between a
communication class and the GUI, and one for checking if the wlan is
connected or disconnected. We use several unmanged calls to enable complete
control of all the buttons(the power button is not mapped) and also unmanged
calls to a iPAQ specific API which provides information about the
wlan(IPAQUTILWLAN.dll).

Since the problem only ocurs if the aplication is run non stop for several

days, my suspesion is that it could be a memory leak.

Does anybody have an idea what this problem could be caused by? How can I

debug this problem more specificaly by for example getting memory usage and
other low level information. I've tried logging severel informations from
within the program(thread loop count, wlan requests, and other info) but
this is not enough though.