AmiDock hits memory when quit externally

[trixie]

1. Boot into AmigaOS with AmiDock running.
2. Start MemGuard and Sashimi to watch for illegal memory access.
3. Open Exchange, select "AmiDock" from the list, press the "Remove" button, and confirm the action.
4. Sashimi will display a MemGuard hit caused by AmiDock in FreeVec() - Memory already freed.

Can anybody confirm? You must really have MemGuard running, otherwise the hit will go unnoticed.

[kas1e]

@Trixie

Can anybody confirm?

Tried exactly as you describe on my peg2/latest beta: boot, run exchange, press "remove" ok, and it removes well. Serial log is clear, memguard in silence.. I tried and with hard reboot , and with user kernel + memguard and with debug kernel + memguard : no hits.

Just in case: my amidock is 53.35

[trixie]

@kas1e

Could you try it with more than one dock displayed on Workbench? Might be connected to that. Thanks.

My AmiDock is the same version, BTW.

[kas1e]

@trixie
I have 2 docks : one which launcher panel with about 20 icons inside, and one at top of wb which i make like traybar. When i remove AmiDock from exchange they all removes well.. I think about 2 moments:
1) maybe sam specific
2) maybe i need to mimic exactly as you have it (maybe you can put your amidock setting, so i can test).
Did you have the same problem if just use fresh amidock without anything manually added ?

[trixie]

@kas1e

Weird stuff. I'll try to isolate the problem and find out more about the context of the crash.

[trixie]

@kas1e

Might have been a false alarm: I can't reproduce the hit any more. Will keep an eye on it, and if it doesn't re-appear, I'll close the thread as solved.

[kas1e]

@Trixie
I play with amidock in last week pretty heavy, and only one time i got a DSI, which i can't reproduce at all and which happens when i a loooot of time plays with all kind of settings , change and remove docks, add and remove all kind of stuff from and so on. And that DSI was on moment of apply of some new setting, not when i remove it from memory via exchanger. Maybe some usual things like "already trash memory by some/somewhere and in end it cause a problem for current app".

[trixie]

@kas1e

Maybe some usual things like "already trash memory by some/somewhere and in end it cause a problem for current app".

Yes I may have trashed the memory by my own code, which probably caused AmiDock to produce the hit. But I must have spanked the memory real hard, because the hit kept re-appearing even after a couple of resets