sokeefe
7th July 2009, 03:20 PM
I currently have an issue with a Windows Mobile application that appears to be dropping out of memory at random points. This is happening on many different types of PDA's, and it doesn't seem to catch an exception in any error handling throughout the application. I have placed logging throughout the entire application, to try and determine what could be the cause. During one of the drop offs, the section of code directly after the last successful log entry was just boolean checks on local variables, and the next log entry wasn't hit. There were no web service calls being hit, and no database access calls being sent, just these simple lines of code.
The application is written in the Microsoft .NET 2.0 Compact Framework. I have actually made a test application that just has two timers, running simultaneously. One timer makes a basic database call to a mobile database, and one makes a web service call. This application also would drop out, with just this code. The main application is very large and I wanted to eliminate any other .dlls or projects that we have added in the solution. It makes me think there is something in the .NET Compact Framework that is the issue.
I did read the following post from the Microsoft Site:
http://social.msdn.microsoft.com/forums/en-US/netfxcompact/thread/de556282-b2ec-4c1f-8bac-d647b4103a2b/
This seems like a very similar issue. I tried installing the 3.5 Framework, and at first I thought that this helped the problem, as the dropout occurred less frequently. Running through the application after this, however, the application still drops out. It seems to have limited the amount of times this occurs, yet still happens. This phone that I'm using definitely has the issue more that others, rarely being able to complete the process without the application dropping out of memory.
Has anyone had any of these issues developing with mobile applications? This has been an ongoing issue with our applications, and any help would be greatly appreciated. Thanks,
Steve
The application is written in the Microsoft .NET 2.0 Compact Framework. I have actually made a test application that just has two timers, running simultaneously. One timer makes a basic database call to a mobile database, and one makes a web service call. This application also would drop out, with just this code. The main application is very large and I wanted to eliminate any other .dlls or projects that we have added in the solution. It makes me think there is something in the .NET Compact Framework that is the issue.
I did read the following post from the Microsoft Site:
http://social.msdn.microsoft.com/forums/en-US/netfxcompact/thread/de556282-b2ec-4c1f-8bac-d647b4103a2b/
This seems like a very similar issue. I tried installing the 3.5 Framework, and at first I thought that this helped the problem, as the dropout occurred less frequently. Running through the application after this, however, the application still drops out. It seems to have limited the amount of times this occurs, yet still happens. This phone that I'm using definitely has the issue more that others, rarely being able to complete the process without the application dropping out of memory.
Has anyone had any of these issues developing with mobile applications? This has been an ongoing issue with our applications, and any help would be greatly appreciated. Thanks,
Steve