strange behaviour

  • Thread starter Thread starter Mark Irvine
  • Start date Start date
M

Mark Irvine

Hi,

I'm having a rather strange problem with a c# app that I wrote, every now
and then - no pattern at all, the close method appears to be automatically
called and the application closes down. This has happened to me a few
times, but I can't understand why. On most occassions this happens when the
user taps the start menu and opens another application. Has anyone come
across this before?

Mark
 
If the system is running low on memory it will try to close applications and
if your app is relegated to the background it will be eligible for this
"cleanup". You need to design your app to save it's state so a user can load
it and resume from wherever they left off. Also look at the memory usage of
your app (or other apps running concurrently) and see if you can reduce
this.

Peter

--
Peter Foot
Windows Embedded MVP
www.inthehand.com | www.opennetcf.org

Do have an opinion on the effectiveness of Microsoft Windows Mobile and
Embedded newsgroups? Let us know!
https://www.windowsembeddedeval.com/community/newsgroups
 
Peter,

Many thanks for the prompt reply. Part of the closing procedure is to ask
the user if they want to save data, so state is maintained. I chedked the
memory status and 48MB free for programs to use. It does also happen
sometimes when in the application. I'm very confused.

Mark
 
Hi,

This problem has really been confusing me, but I've noticed other programs
are being closed down as well, e.g. File Explorer. However this only seems
to happen, or at least more frequently, when the device is docked. Once
undocked I've not seen any occurance myself, although some users have
reported that the app does close down sometime for no reason.

Mark
 
Do you have any sync applications which auto-start on dock aside from
ActiveSync itself?

Peter
 
What is your device? I think you might be reaching an active process limit.
This will force come apps to close even if you have plenty of memory
 
Alex,

I'm using the XDA 2 (from O2) powered by pocket pc 2003. Is it possible to
change this limit?

Mark
 
Peter,

Many thanks for your reply. I was running version 1.03.00 so I downloaded
the upgraded ROM. Things are a bit better, the device now seems to allow
four applications to run before shutting others down - still very strange
seeing as there is lots of memory available. Something new learned today :)

Mark
 
Another suggestion is to remove the O2 Active and other OEM installed
applications from the \Windows\Startup folder - e.g. IA Caller ID etc. This
will give you a few extra processes to play with. In the case of O2Active
you can remove it completely from Remove Programs application.

Peter

--
Peter Foot
Windows Embedded MVP
www.inthehand.com | www.opennetcf.org

Do have an opinion on the effectiveness of Microsoft Windows Mobile and
Embedded newsgroups? Let us know!
https://www.windowsembeddedeval.com/community/newsgroups
 
I asked the question precisely because I suspected the answer will be XDA2.
Your description had all the right signs of the infamous
XDA2-running-out-of-available-processes issue. The limit is a hard
restriction in the OS, but following Peter's advice should let you alleviate
the problem
 
Alex,

And you are correct! The ROM has improved things, was a bit worried in case
it was my code :) I had not heard of this problem before.

Thanks again for your help.

Mark
 
hi all,

I saw the same problem on device Fujitsu Loox FLX3AW. It's really
anoying. I heard about memory problem in this group but it also
happens in case of no other application to be run, and memory is much
available. I assume the reason is the conflict between device hardware
and .NET compact framework(just assume).
I also heard about the bad quality of Fujitsu device, but I have no
chance to experiment on other devices. In the other hand, actually it
is difficult to reproduce this phenomenon.
Pls share information if knowing how to overcome.

Thanks,
Khanh
 
Back
Top