CF 2.0 application sometimes freeze strangelybehaviour

  • Thread starter Thread starter Enrico Pavesi
  • Start date Start date
E

Enrico Pavesi

I have a CF 2.0 application that runs on a WM2005 device (Symbol MC70).

Sometimes (rarely) seems to freeze, that means the screen does not respond.
If i switch off and than switch on terminal (not a reset just suspend
resume), the application start responding again.
There is no exception ( i log everything), just the screen that beeps, but
non imput arrives to the application

Do you know wich can be the cause of this strange behaviour ?
May be a O.S./firmware problem?

Thanks in advance
 
Have not seen your application, but If I were you, I would start to
analyze your working threads. Maybe in some cases they consume too much
resources.

If you have only UI thread - please give more details; describe at which
forms you see this strange behavior; otherwise we can't help you.
 
There is only one UI thread...the form is not always the same ...
two times that it happened i had just connected or disconnected ActiveSync
and the application was idle for 4 o 5 minutes.

No error so i do not have any information on what "freeze".

I understand that is strange, just wanted to know if someone else has ever
seen it.

Thanks




Sergey Bogdanov said:
Have not seen your application, but If I were you, I would start to
analyze your working threads. Maybe in some cases they consume too much
resources.

If you have only UI thread - please give more details; describe at which
forms you see this strange behavior; otherwise we can't help you.

--
Sergey Bogdanov [.NET CF MVP, MCSD]
http://www.sergeybogdanov.com


Enrico said:
I have a CF 2.0 application that runs on a WM2005 device (Symbol MC70).

Sometimes (rarely) seems to freeze, that means the screen does not
respond.
If i switch off and than switch on terminal (not a reset just suspend
resume), the application start responding again.
There is no exception ( i log everything), just the screen that beeps,
but non imput arrives to the application

Do you know wich can be the cause of this strange behaviour ?
May be a O.S./firmware problem?

Thanks in advance
 
Back
Top