I hope that this does not concern the call MemHeapCompact(0).
Keith, what about some statement about the suspected NVFS bugs? We are
loosing hours and days and Palm has nothing to say?
Imagine the customer reaction that I met lately: "Never mind that your
backup does not work. It's NVFS fault. All backup programs have the same
problem..."
I don't expect any apology, but an advice that could let us return to our
business.
Maybe somebody else from PalmSource/PalmOne?
Best regards,
Jan Slodicka
----- Original Message -----
From: "Keith Rollin" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[email protected]>
Sent: Thursday, March 03, 2005 9:08 PM
Subject: RE: about memHeapCompact on NVFS devices
> Hi,
>
> It seems to me that calling MemHeapCompact would be a bad idea on NVFS
> devices, regardless of any bugs. By doing that, you are causing the
> shuffling of memory more frequently than would otherwise occur. This
> shuffling of memory would cause more rewrites to the same blocks in the
> flash, typically towards the lower end of the memory range.
>
> Unless there are any smarts in MemHeapCompact or the rest of the Memory
> Manager to support "wear levelling", this rewriting will shorten the
> life-span of the flash, possibly leading to part failure.
>
> So, unless I had a good reason to call it, I'd stay away from
> MemHeapCompact.
>
> -- Keith
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of
> > Regis St-Gelais
> > Sent: Thursday, March 03, 2005 4:52 AM
> > To: Palm Developer Forum
> > Subject: about memHeapCompact on NVFS devices
> >
> > I've received an answer from PalmOne about the memHeapCompact
> > bug on NVFS devices.
> >
> > Here is a copy of Sangram Singh post on PalmOne's NVFS Expert Event:
> >
> > <QUOTE>
> > RE: MemHeapCompact on NVFS devices (T5 in my case) Posted Mar
> > 2, 2005 by Sangram Singh
> >
> > Hi Regis,
> > We have noted the issue and we will update our NVFS White
> > paper to reflect this.
> > Unfortunately, at this time there is no workaround for this issue.
> > Thanks,
> > Sangram
> >
> > </QUOTE>
> >
> > My question was:
> >
> > <QUOTE>
> > MemHeapCompact on NVFS devices (T5 in my case) Posted Feb 16,
> > 2005 by Regis St-Gelais
> >
> > it looks like one must not call MemHeapCompact when there are
> > openned databases. If you do so it will result in a crash.
> > If I compact only when all my databases are closed, I dont
> > have any problems but I am concern that other applications
> > might have some oppened databases.
> > I dont think it would be safe to call MemHeapCompact at all.
> > The docs says that the OS can call this function when needed
> > so I am a bit consern.
> > Also, I usualy do a MemHeapCompact after massive database
> > edition/deletion to defragment the memory.
> > So how do we defragment the memory on the T5 ?????
> >
> > Here are 2 links on that topic on palm-dev-forum
> > http://news.palmos.com/read/messages?id=178642#178642
> > and
> > http://news.palmos.com/read/messages?id=181579
> >
> > </QUOTE>
> >
> > For those of you who have a pluggedin account, here is the
> > link to the expert event tread:
> > http://developers.palmone.com/pe/forums/displaypost.jsp?postID
> > =10134889
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/support/forums/
