i have the same problem on htc touch hd wm6.1. i was testing rungps( 2.3.6c build 1961) in during the last days. It an amazing tool - very great. but this bug holds me off from buing it.
As I know, WM6.5 indeed has changed memory handling but as I know all 6.5 versions have the same.
I just tried it again with only 56MB RAM free: Started Run.GPS in portrait, switched to landscape, opened training log, opend detail page for a training (this crashed ALWAYS on my 6.1 ROM in landscape), switched some times between portrait/landscape, change to map view (in landscape), open map settings ...
I have same problem, on 1961 build and 6.5.3 ROM.
Probably memory is fragmented, right after restart everything works ok.
Maybe 6.5.5 has better memory management.
Did You try to switch to landscape mode after longer pda uptime? Run few programs and close them, then run run.gps and check if it still crashes.
(sorry answer is in German because I already prepared this in German for an email)
Also das Problem ist wohl folgendes: bei dem Trainingslog-Dialog wird eine sehr große Zwischenbuffer-Bitmap benötigt. Diese muss in der Breite des Dialogs und in der Höhe aller scrollbaren Elemente im Dialog im Speicher angelegt werden. Dabei gibt es häufig das Problem, dass Windows Mobile nicht genügend *zusammenhängenden* Speicher bereitstellen kann, obwohl massenhaft Speicher frei ist.
Leider haben wir für dieses Problem noch keine Lösung gefunden. Ab einer bestimmten Größe des scrollbaren Bereichs schaltet die Darstellung von Pre-rendering aller Elemente auf das on-the-fly-rendering um (ohne kompletten Scrollbereich im Speicher). Scheinbar ist diese Grenze für das Xperia im Landscape-Modus zu gering eingestellt. Wir werden das mal auf einem Touch HD ausprobieren, welcher ja ungefähr die gleiche Auflösung hat.
17.03.2010 14:53:46 UTCgeändert am 17.03.2010 14:56:03 UTC
I changed from an ASUS A696 (QVGA) device to a Sony Ericsson Xperia X1 (WVGA).
I use the original SE R3A Rom (latest available) and if I use Run.GPS in landscape mode I get very often "Out of Memory" Errors even if there are 115MB of Memory free.
I can reproduce this in the following ways (there is 120MB RAM free before starting Run.GPS):
1. Sometimes I get the error immediately after starting Run.GPS. Then sometimes it works if I use a tool like CleanRAM to create some more free memory. Sometimes only a Reboot can solve this problem.
2. If I change from Portrait to Landscape while Run.GPS is running (I use a Hardware key for this) I get the "Out of Memory" error with a 90% chance.
3. If I start Run.GPS in Landscape Mode and go to "Logbuch und Planung" and I select a Training the "Out of memory" comes every time. In portrait mode this works most of the time.
This is really annoying since Run.GPS worked perfectly on my ASUS in QVGA resolution and was absolutely reliable. Now if I start a Training I fear pressing any button in Run.GPS just because this "Out of Memory" issue.
Is there anything I can do that this problem does not occur? I think many WVGA devices will have the same problem because they use 5 times the memory for the graphics and I think there is the problem. I think Run.GPS uses big bitmaps for displaying the UI and there is a limitation in this bitmap size.
I'm using Run.GPS 2.3.5 Build 1910. Will try the latest 2.3.6 but I think that this memory issue will be still there.
@developers:
can you please have a look at this issue if you can reduce the memory usage a bit? A good start would be if the program won't close completely when this error occurs while opening a sub dialog.