ScummVM and AmigaOS4.1 F.E.

@Mr_byte

don't bother with "kill"ing a crashed app...that option is there just for "fun"...it does nothing actually, the crashed app will either way stick around (in memory) and cause havoc nonetheless

well, as I said, it could be anything...

@mr_byte

maybe another user with the same hw can jump in and do a cross check...maybe its the system, maybe its bad ram, maybe a seagull shat the technician responsible for the inner workings of your hw on the head on his way to work and he was so angry he forgot to check a solder point, maybe its monday, maybe your hdd is borked, maybe i should stop, maybe i should go on, maybe...maybe

@Raziel

Quote:

GREAT NEWS Raziel!! :)

I did this. I added a line and started scummvm. Exited Scummvm and turned off the machine and started with the next line etc. I occasionally got error messages on exiting the program and sometimes on startup as well. But the problems became constant when I added the path to the plugins folder. I renamed plugins to plugins2 and created an empty plugins folder. Now svummvm starts and exits successfully every single time without error messages on startup or exit. I can change settings to OpenGL and Window mode without problems. I couldn't start my games, so I added scumm.plugin, wintermute.plugin, agi.plugin and sci.plugin from the plugins2 folder to the plugins folder. Still completely stable and the lucasarts and sierra games I've tested have worked brilliantly and I can exit to the launcher without a problem.

Does that mean I have to add one plugin at a time to see which one is causing the problem?

@Raziel

Quote:

You do a great job and I envy you for your knowledge. Everyone can feel burnt out once in a while and it's okay to take a short break if you feel the need to. Motivation goes up and down in waves. I can happily donate a little for a pizza and a beer to show you that I appreciate your work

@Mr_byte

hmm, so its one of the plugins...interesting

you can try and get the latest build from my cloud (yesterday or today, not sure)

if you get a crash, dont click on "kill", rather get more information, create a stacktrace and take a look at the plugin that is (hopefully) showing up there

how much memory do you have?

@Raziel

I downloaded build 2024118 today.

I startet it up and it created a scummvm.ini file. Startet again and it crashed like before. I created a stacktrace and the agi.plugin has a reference there (strange as agi.plugin was one of the plugin i keept when i got i working last time). I removed agi.plugin to see what happened next (I always turn the machine off and on between each error message). Next error message was about composer.plugin. Removed that and the next one was about crab.plugin. So in alphabetical order that is.

When i just keep a few like scumm.plugin, wintermute.plugin, agi.plugin and sci.plugin, everything works perfect with the 20241118 build like earlier today. Looks like its something about the quantity..


By the way, I have a 4GB memory stick in the machine. Where 2GB is visible in AOS4.1 as you know.

@Mr_byte

what version os your newlib and elf.library

and your ogles2.library version, size and date, please

it sounds like you suffer from the shared objects bug we had earlier...two years or so

@Raziel

Quote:

The ogles2.library is 3.4 from @Mr_byte you see it further up in the thread. I also had this lib in this version on my A1222 and there were problems with the textures of Billy the Frontier https://os4depot.net/?function=showfil ... /action/billyfrontier.lha

Daniel fixed it later, but I don't think that will be the problem here.

@Raziel

Elf.library 54.1 98.708 bytes 7 December 2023
Ogles2.library 3.4 WIP 2.503.592 bytes 27.September 2023
Newlib.library 53.84 797.316 bytes 24 July 2023

Does it look okay?

@Mr_byte

i only have newlib 53.80, probably your hardware got an update.

yeah, its alright.

i did remember some old crash, that went away eventually unnoticed...at least on my setup (it also changed during the course of searching for a reason, so...random means bad and likely even harder to find/fix)

do the following
remove from plugins/
groovie.plugin
plumber.plugin

simply move them somewhere else and try
if it works, do a thorough test with different games, return to launcher, settings, ADDING GAMES, quitting, etc

if those two engines are really the reason, then I'm baffled...

@Raziel

Quote:

Unfortunately, removing these did not help.

I made a copy of the full plugins folder and created a new empty one.
And started by moving over plugins in pools like axxx.plugin. For each pool i Started scummvm, start a game, return to launcher and exit scummvm. If it crashed somewhere in the process, I removed one plugin at a time until I found the one that caused the crash...Very difficult as it could look like a plugin was working, but then it would crash maybe 50 percent of the attempts

Very time consuming and don't know how useful it is for you..

I am attaching a screenshot. The folder called "bad?" contains plugins that cause problems for me if they are in the plugin folder.

With the files that are in the ordinary plugin folder in the screenshot at the moment, i can complete a very simple test: Start Scummvm without errors. Start "the dig", return to launcer and then start "Gabriel Knight 2" and return to launcer again. And then exit scummvm without error messages.

As you can see, I haven't been able to check all the files..but groovie.plugin and plumber.plugin did not cause any problem for me with my simple test.

Try to increase the stack a lot and run scummvm

@Mr_byte

everything helps, but my idea was a shot in the dark...try the stack as @afxgroup mentioned

@afxgroup

Quote:

By clicking the scummvm icon and clicking information, right?

I first increased the stack size from 1mb to 4mb and scummvm actually started up with the original plugin folder! I started a game and selected return to launcher and then Scummvm crashed. I turned off the machine and tried to start scummvm again without touching the stack size i adjustet. But scummvm crashed again during startup as usual with the full plugin folder. I tried turning the machine off and on several times and trying again. I then changed the stack size to 2mb and tried again. Then scummvm actually started up as normal again. I clicked quit and tried to start scummvm again and then it crashed again like before. Tried rebooting the machine and starting scummvm several times with no success. Tried increasing the stack size to 8mb and even higher. But it wouldn't start at all when I tried that high. Stacktrace only started to only mentioning newlib and not the plugin files when the stacksize got too high.

So I got 2 successful startup attempts, which I couldn't repeat twice with the same setting..

@Mr_byte

since you use a different newlib version I'm inclined to blame this

not sure what else to try, other than your workaround to temporarily drop the "bad" plugins

i don't think they really are the culprit, I'm pretty sure it will still crash even without them

there's something else that isn't quite right...

@Raziel

I live really well with a plugins folder with only a handful of plugins that make my selected games work together with the interface that also works stably with the few plugins..For that use, it is stable as a rock and i cant get it to crash whatever i do. If you want to share your newlib version, i can try it out for a moment to see if there is a difference.

@afxgroup

I got hold of your clib4 version of scummvm from Maijestro. It came with clib4.library 1.0. Worked fine on my A1222, but i needed to update to clib4 1.3.0 to be able to play the wipeout SPE port from HunoPPC. But your version of ScummVM did not work with clib4 1.3...Is it a easy fix to make it compatible? I can of course change the libs around when i need them..but a little stressfull

Thanks :)

With an hex editor..

@afxgroup


Thanks for the hint

I'm not very good at this. But I will try my best I understand that with a hex editor that I can search for a reference / value and change it to something else. But I can't figure out what to change...Sorry. I found a few ascii references to clib4...