Amiga.org
Amiga computer related discussion => General chat about Amiga topics => Topic started by: kolla on December 21, 2022, 09:15:16 PM
-
They should have hundreds of megabytes for that price. This product does not have enough RAM to even boot any non-ancient AmigaOS (OS3.5 or later).
Nonsense, just drop all that Reaction BS that isn’t required for anything marginally usefull anyways and 3.2.1 it boots just fine!
Am I pulling your leg?
You betcha! But really, RAWBInfo and ASyncWB are memory gobblers, at least one of them seem to eat more and more ram over time as well. Consider this a bug report, you guys prefer to collect bug reports like this, so be it.
You current OS h4x0rs should be forced to test all your bloat on 68000 systems with 2MB of RAM tops. Did I say test? I mean use.
-
No ReAction classes are opened during startup so their presence isn't going to affect the amount of RAM needed to boot the OS. The first time the AsyncWB or RAWBInfo windows are opened, several classes will be opened, which will of course cause a loss of memory until they are explicitly flushed by the user, or the OS needs to do so, the same with any other library.
I'm not getting any memory leaks here on a vanilla install. If you have a specific sequence of actions that result in a leak, I'm happy to investigate further and fix.
-
Topic split.
You can continue your pointless comments here. Thanks for derailing the original thread.
-
I'm not getting any memory leaks here on a vanilla install. If you have a specific sequence of actions that result in a leak, I'm happy to investigate further and fix.
Open your sys: volume, whatever it is called, pick "Utilitiies", select "copy" from Icon menu, let it make a copy, select the copy, select "Delete..." from Icon menu and confirm on the requester.
Repeat till you run out of RAM.
And yes, Avail FLUSH won't give you RAM back.
And yes, it ONLY happens with ASyncWB.
RAWBInfo seems "clean", it just gobbles up another 120 kB for each window it opens, but that RAM is released on closing, and gives back RAM on exit.
-
OK, thanks for the report; this has now been fixed.
-
Nothing is really fixed until update is actually on my disk drive.
Which apparently takes months and years.
And arbitrarily requires me to pay, yet again, for the same crap, only with new set of bugs.
And support Hyperion? Meh!
-
Actually OS3.2.2 is very close to release (currently scheduled for January 2023) and will be a free update.
-
Any info on changes / fixes.
As the floppy and pcmcia issues are really annoying. Yes, if I go back to 3.1.4 both issues are resolved.
-
As the floppy and pcmcia issues are really annoying.
What issues are those? Described where? Confirmed by whom?
-
What issues are those? Described where? Confirmed by whom?
Writing a floppy without verify causes disk errors. Same task with 3.1.4, works perfect every time.
Inserting PCMCIA adapter, does nothing. Removing CF then inserting adapter, then 5 secs later inserting CF into adapter, it takes around 20 seconds to show.
If you are unlucky, it trashes card. Same task in 3.1.4 works perfectly, instantly see's card and adapter without messing about.