Anyone know what would cause a crash in AmigaOS 3.X (from Cloanto's Amiga Forever)

[Nightfox]

Hi all

I am the developer of AmigaGPT and I have received a report and have personally verified that AmigaGPT will cause an entire system crash when switching to the Image Generation tab. This only occurs with Cloanto's AmigaOS 3.X ROM. AmigaOS 3.9 and AmigaOS 3.2 work perfectly.

Does anyone know if the paging via clicktab.gadget is broken in its earliest version?

Here is the issue in GitHub. I have tried to diagnose it by commenting out a lot of code to try to create more stable code but it still crashes. I'm wondering if anyone has any clues as to what could be causing this?

https://github.com/sacredbanana/AmigaGPT/issues/6

An easy way to replicate this is to have a new installation of AmiKit and install it via Amiga Forever.

I am assuming this also crashes on real Amigas running the 3.X ROMs.

I'll continue to try to investigate over the coming days but any help, or direct pull requests to fix the issue would receive infinite love <3

[Minuous]

"AmigaOS 3.X" is full of obsolete and mismatched components, it's no surprise it doesn't work. I gave up trying to support that a long time ago.

[Nightfox]

yeah its been nothing but pain rewriting my code constantly whenever 3.X breaks T_T

[Snoopy1234]

Jens Schoenfield at Individual Computers has spoken of his differences with Mike from Cloanto. He doesn't support 3.x at all saying Mike is too brutal an approach - "We are a creative community, don't break it"

On the other hand, I have a 3.x A1200 setup aside from my 3.9 A1200 and it's a clean an sharp environment - so whatever.

This quote from the Cloanto site says 3.x systems need workbench.library on the boot disk as it's no longer in rom.
"The 3.X ROMs have a size of 512 KB, and are therefore compatible with all Amiga models except for the Amiga 1000. In order to make room for the enhancements, the 3.X ROMs employ the same technique used by Commodore for the 4000T ROMs, i.e. ROM space was freed by moving workbench.library out of the ROM. This means that a "Libs/workbench.library" file must be present on the boot disk, as detailed below."
https://www.amigaforever.com/kb/16-125

[Minuous]

The main problem is not so much the "3.X" ROM (though there are probably mismatched component versions in that too) as the on-disk components such as ReAction.

[Nightfox]

AmigaGPT is bundled in current and future versions of AmiKit. The reason why I'd like it working with a 3.x environment is because installing AmiKit via Amiga Forever (which installs 3.x) is one of the installation options. Also because the guy behind AmiKit, Jan, is super awesome and asked me kindly to see if I can fix it.


And yes that's right, the contents of the ROM isn't the issue here. It's more the issue with the old gadgets in its included ReAction suite

[Snoopy1234]

Amikit has ReAction and MUI installed when the Wiki says they're not compatible with each other. Would system resources be allocated to both?


https://wiki.amigaos.net/wiki/ReAction

[alexh]

Originally Posted by Snoopy1234

Amikit has ReAction and MUI installed when the Wiki says they're not compatible with each other

That's not what it means. It means source level / API compatible.

i.e. you can't just compile an MUI application to use ReAction and vice versa.

It's normal to have ReAction/ClassAction and MUI installed at the same time.

[Nightfox]

While mildly on the topic of MUI, would it be worth porting AmigaGPT from ReAction to MUI? Is that difficult? I've never used MUI before.

[alexh]

I imagine it's just a matter of converting the API calls. They are probably extremely similar but as mentioned above not 1:1 compatible.

I wouldn't bother unless you were extremely interested. All Amiga users today have an environment which supports both.

[Nightfox]

Actually I've seen a lot of messages from sad people wanting to run AmigaGPT on AmigaOS 3.1 which doesn't have ReAction

[Don_Adan]

This problem/crash is related to Amiga 3.X kickstart or 3.X system?
From my memory Amiga 3.X kickstart is Amiga 3.9 kickstart only.
With some patches/fixes from Aminet.
Of course some Aminet patches dont looks good for me.

BTW. Dont use MUI. MUI is BAD.

[Nightfox]

its most likely related to the oldest versions of the ReAction gadgets included with an Amiga Forever 3.X install.


MUI is bad. ReAction is bad. I just want to know what is the lesser of 2 evils lol. I wish there was a decent GUI library for m68k Amiga

[Don_Adan]

ReAction is less bad than MUI.
3.X has the latest versions of Amiga components, I think. Some with problematic "fixes".
Maybe try with more stack, f.e
c:stack 16000

[Nightfox]

haha the icon file starts up AmigaGPT with stack 20000 already

[Don_Adan]

He can run from CLI.
And strange report.
No CPU, no memory, no guru number.

[Nightfox]

same things happen when I run from CLI with a stack of 32768.

And no there is no guru number because what happens, (at least in WinUAE in AmiKit with 3.X) is the system just freezes entirely

[Don_Adan]

Crashing at first time? Or after some attempts?
If after some attempts, then perhaps stack is not restored correctly after some action(s).
In general using stack is also BAD.
Better is using normal data memory.

[Nightfox]

crashing every time you switch tabs to the Image Generation tab (powered by clicktab.gadget). The reason why I said sometimes is I noticed it works sometimes if you have a certain number of chats and/or image generations in your history but that could just be coincidence. so far in my current setup im able to reliably get it to crash every single time

[Nightfox]

Also, I use heap memory as much as I can nowadays. I limit my use of stack