Is there any memory defragment to use with the memory is very fragment and the only option is reboot, but you can't?

Quote:

It is not possible to defragment memory.

Quote:

ufffss. Thank you for your answer.

Other question:
----------------------------------------------------------------------
12:25:41 04-nov-18
68k Exception 2 <Unknown Exception>
Task 0x16ac3120 <VAMP>
Dn[0] 00000010 00000010 16b77be8 16b77be8 00000000 16b77910 00000000 16b066a8
An[0] 16ff7120 140c4ba8 00000000 00000000 16ff72b0 0001bf2e 14001948 00000000
PC ec400000 SR 1133

This log tells me that there is a 68k program although the VAMP program be a PPC program?

Do you mean actual fragmentation of physical contiguous memory? Or the slowdown caused by the lengthening of the allocation table over time (because in vanilla AmigaOS it is a linked list that is traversed every single allocation)? On anything Amiga-related people constantly confuse the two.

MorphOS helped the first problem and completely removed the latter (AFAIR, anyway).

https://library.morph.zone/In-depth:_The_New_MorphOS_Memory_System

And how do you even know your memory is fragmented and not simply allocated by stuff that can't be flushed?

[ Edited by KennyR 04.11.2018 - 18:14 ]

Quote:
Well, using OWB, after of visit much sites or to have several windows with sites using javascrit, the system and the browser crahsed, I have only 512 mb and I can't add more, using only the 512 the OWB fragment very much the memory and it leaves fragmented even exit the program.

You're saying that OWB crashed not deallocating the memory so you had only 512 MB available of 1 GB left?

Or do you mean that you got back all the RAM after OWB crash but somehow half of it became unusable?

Quote:
The second explanation. And only my computer cants to has 512MB.

Unfortunately it's quite a big problem with OWB. 512 MB is nearly unusable.

@KennyR

Not necessarily caused by Odyssey, though.

Try to use an iPad 2 with 512MB of memory to browse the internet these days. Not a pleasant experience. Frequent browser crashes due to insufficient memory, etc.

Quote:

Yes, it's just how modern browsers are. OWB isn't cutting edge but it's modern enough to need bucketloads of RAM. Disproportionately more than anything else on MorphOS.

When you've only got 2 GB of address space and no virtual ram to swap it and back and make the physical memory contiguous again, the problem of heavy memory usage tends to be even more acute.