Does anyone know how to deal with memory in an application ?
RoadMap sometimes won't start up again saying "no more memory",
sometimes the device just displays the "busy cursor" for a second and
then doesn't start the application at all. (Nothing in the application's
log.)
I am guessing that this
On Sat, 18 Oct 2008, Danny Backx wrote:
> Does anyone know how to deal with memory in an application ?
> RoadMap sometimes won't start up again saying "no more memory",
> sometimes the device just displays the "busy cursor" for a second and
> then doesn't start the application at all. (Nothing i
I have no experience, but, did you try testing by running application a few
times and going to Settings->Memory and comparing?
On Sat, Oct 18, 2008 at 09:19, Danny Backx <[EMAIL PROTECTED]> wrote:
> Does anyone know how to deal with memory in an application ?
> RoadMap sometimes won't start up ag
On Sat, Oct 18, 2008 at 09:40, Vincent Torri <[EMAIL PROTECTED]> wrote:
>
>
> On Sat, 18 Oct 2008, Danny Backx wrote:
> > Do you need to clean up everything when terminating the application ? On
> > UNIX and its friends, you don't. Also the doc says that ExitProcess()
> > kills all threads. Is thi
On Sat, Oct 18, 2008 at 10:50, Vincent Torri <[EMAIL PROTECTED]> wrote:
>
>
> On Sat, 18 Oct 2008, Ivan Vucica wrote:
>
>> Vincent, those sentences refer to a _*currently running_* application, not
>> to a recently terminated. This paragraph implies that WindowsCE _does_
>> perform a cleanup.
>>
>
On Sat, 18 Oct 2008, Ivan Vucica wrote:
> On Sat, Oct 18, 2008 at 10:50, Vincent Torri <[EMAIL PROTECTED]> wrote:
>
>
> On Sat, 18 Oct 2008, Ivan Vucica wrote:
>
>> Vincent, those sentences refer to a _*currently running_* application, not
>> to a recently terminated. This paragraph implies tha
On Sat, Oct 18, 2008 at 11:13, Vincent Torri <[EMAIL PROTECTED]> wrote:
>
> so, the case where the program gets informations continuously from internet
> and stores it in a single linked list, and the program does not free it
> (because it needs it during all its execution), except when it finishe
My experience with WinCE 4.2 with writing gosmore is that you can run out of
memory by using new GDI objects for each Expose(), like pens and not free
them. Then the whole operating system can become pretty unstable.
Gosmore allocates (potentially) large routing arrays but always 2 or 3 MB
less th
My experience with WinCE 4.2 with writing gosmore is that you can run out of
memory by using new GDI objects for each Expose(), like pens and not free
them. Then the whole operating system can become pretty unstable.
Gosmore allocates (potentially) large routing arrays but always 2 or 3 MB
less th
