Hello dear Amigans ooopps, MorphOs users. :)
What is yours max UpTime on MorphOs machine?
I am MoprhOs user which uses Macmini for all computer jobs. So, most time I open OWB, AmimetRadio which streems audio station for 1-2 weeks t. I also uses Modeler and from time to time and Lw renderer. (and JbgtoMov, pure 68k software)
Most time my Morphos machine is very quick, but after 2 weeks of using (all staff together) I found memory is very unpredictile "full"?.
As I have only one Gb of memory I found I must reset my system to have free memory after 2 weeks.
I don't test any more compaibility with old software, I just use what I have from classic amiga (and just do working done) and my sistem Is joy to use.
My question is, can I use some, or of any kind of software for better memory defragmet. (68k?)
I found that I have about 600Mb of free space of 1Gb, after week or two without reset, very fragmented and I can't even open Mplayer to watch mov file because of "bad" fragmantation of memory.
This is more than enough time to do all I can, but I like multytasking of our system and when I render many images, I can't just sleep behind monitor, so I do other thinghs but memory is a problem. (but is not, if you look at Ambient bar)
Software in use most of time is:OWB, AminetRadio, Modeler(68k), Lightwave (68k), Hollywood, MPlayer, FxPaint, Showgirls, JpegToMov-Mencoder, and MorphOs system software.
All in all I don't cry about that freaking reset, I just wanna avoid to open all my software and docs again to continue.
MorphOs just rulezzz and I enjoy to use it!!!! :)

MorphOS is using an advanced memory system, which takes care about fragmentation.

I have MorphOS running as a server 24/7 with multiple applications. If you run into memory issues, then it is the software you are using, which is loosing memory for some reason.

Two weeks is really long. I dream of that. I only use OWB, YAM and some onboard tools most of the time but because of OWB's memory consu,mtion I have to quit it very often. OWB does not give back all memory, when I run avail flush afterwards it frees a lot more memory. but after 2 or 3 days it is so fragmented that OWB crashes on every request of opening a new page. then I have to restart the machine. Also Mac mini 1GB.

Quote:

C'mon, are you living in a world of unicorns? Even Fab said, OWB's engine would benefit from vmem...

Quote:

The engine would benefit more from fixing the memory leaks than adding virtual memory. Recent OWB is over a year old. Maybe the leaks already got reduced (i do not beleave in wonders).

Also it makes no real sense to have vmem as you cannot have more memory than the OS can handle.

So even on a PowerMac G4/G5 or PowerBook with 2GB of memory you can only have 2GB in total. Hence why only 2 GB can be used? Because AmigaOS was a just a 31Bit Operating System.

You will never get more than 1.5 GB RAM on any MorphOS 31Bit System. I have 1.5GB on my work system. It just takes a little longer until OWB has eaten all the additional memory, too. More memory will just delay the appearance and not fix the real problem.

I just quit and restart owb, when the memory sbar turns red. Problem worked around without adding tons of slowness.

Virtual Memory only helps a little, as it just can emulate having up to 2GB of real memory. So better use real memory.

Do you really want a system that read/writes all the time? That is what you get. VMem does not just kick in when needed. vmem needs real memory to work. The more the better. VMEM may be a solution for old 68K systems, which hardware was limited to somewhat 16/32/64/128MB with turbo card, but these days you loose more than you win.

Quit OWB from time to time and nothing happens. The system stays stable unless you run broken stuff. I have my Peg2 with 1GB running 24/7 for several month without any issue and I even use OWB on that system from time to time.



[ Edited by geit 01.04.2015 - 17:20 ]

Ok, let's start teasing Fab for version 1.25

Quote:

Yes, I think that LW/Modeler don't do good job with freeing memory, and OWB sometimes hit that problem also.
I am aware of that and I know how to avoid most problems with our software. (before I test programs which I use on my A1200 also)
Simply I don't use some thing that can do crash (like some LW/Modeler arexx scrpits) and I restart OWB from time to time (when memory is below 100Mb). Cool factor is that OWB will reopen all my tags and I don't loose nothing, only time to reloading pages again.
I see my memory with Fragment ( its look like Super Mutant after Minigun treatment), so I ask can we move that holes on end of memory map with some software. :)
I wanna avoid necessary testing of some 68k memory programs if this is simply no go for MorphOs.

You cannot move memory blocks once they are allocated by applications. This is impossible.

The only way is to quite and restart all applications and perform an avail flush inbetween.

Also OWB returns all memory after quitting as it is pooled. You may need to call avail flush to unload libraries, fonts and other stuff.

Quote:

Thank you for saving my time.
I don't have idea how memory is working, I know that we have CHIP and FAST memory
(and some holes without one free memory chunk, big enough to ran something) and thats all. :)
I also didn't know about avail flush command, I will try that.
During that period I was restarting some programs and I was aware of few MB of memory lost, so maybe this command between will help for avoid this holes.
Thanks and best regards

> Recent OWB is over a year old.

https://morph.zone/modules/news/article_storyid_2131.html

The used WebKit version is, though.

> I know that we have CHIP and FAST memory

Do we on MorphOS?

Quote:

...and that is the question. :)
Name it expansion or explosion memory after weeks of use, LW asking for FAST memory to work.
It is better to tell a new memory name to that old renderer, maybe will help to solve memory leeking.
You can do it. :)

Joke aside, after last avail flush command I got frozen task/shell/MUI console server.
I save log and screenshots and now I have first frozen task. :)
As only ANR is working in backround during last avail flush command I asume that ANR is wrong for crash.

Quote:

Yeah, avail flush often reveals broken libraries. I guess a used player is causing the issue or the mem handler inside ANR itself. In such case a library removes itself from memory, even it is used by at least one application.

And no. There is no "Chip"-Memory on MorphOS. Also there is no gab in memory. Chipmem is only simulated to be available to satisfy old applications, but you will get the same type of memory.

Quote:
Right, look at the start address in Fragment, it's the same (beside the vector offset).