Error in AN5: "Invalid chunk ptr"

[PeterJ]

I got the following error message:
"MemoryMgrNew.c, line 4183, Invalid chunk ptr".
And then "reset" is my only option.

I get this everytime I go to Options > Preferences, open the list at the top right (alarms, contacts, meetings, etc) and when the list is open and visible tap the "home" button (on the left of the graffiti area).

I get the error message everytime I repeat the above steps.

I have the demo version of AN5 and it is running on a Palm IIIe.

Kind regards,
Peter.

[jvarior]

Yeah!

Not got this error on 5.0, on a m505, but my wife gets this error too, on a IIIXE, and does a reset everytime! Happens when she creates a ToDo, and tries accessing Contact details. Even when the contact exists, it brings up 'Create New', and when u try this, it gives the above error. Tried going thru' ConHistory, for old ToDo's, but the same error happens.

I say inconsistent, cause of her 10 ToDo's, 4-5 hv this problem consistently. She uses CFL, with 'Group by Co' turned on, since 4.61! All hacks off!

Any help appreciated, there also seems to be a size difference between my AN and hers. I did try the beta, and then updated. She downloaded the new release on the 8th.

[thomas]

Originally posted by PeterJ
I got the following error message:
"MemoryMgrNew.c, line 4183, Invalid chunk ptr".
And then "reset" is my only option.

I get this everytime I go to Options > Preferences, open the list at the top right (alarms, contacts, meetings, etc) and when the list is open and visible tap the "home" button


Hi everybody, I tried this too and got the same error on the Palm 3xe with OS 3.5.0

Hate to admit ....
Thomas

[b_badger]

Originally posted by PeterJ
I got the following error message:
"MemoryMgrNew.c, line 4183, Invalid chunk ptr".
And then "reset" is my only option.

I get this everytime I go to Options > Preferences, open the list at the top right (alarms, contacts, meetings, etc) and when the list is open and visible tap the "home" button (on the left of the graffiti area).
.

I have been able to reproduce this and have forwarded this to the engineer. This will be fixed on version 5.01.

[jvarior]

That was quick! Was this a IIIXE (3.5x) issue ? Would prefer to revert to 4.61, till new release, if that's the case.

[PeterJ]

Great! Thanks!