now getting random crashes with 5.3 public beta4 april 20.

[vortex222]

I am not really sure what I did. This has actually been happening with a couple of different configs and I cant reliably reproduce it other than to just use the machine. The config I uploaded has a fresh install of 3.1 with 3.1 roms, better workbench v40 and picasso2 drivers. Changing a few settings such as removing z2 ram or removing 2620 ram makes no difference.
This is the same sorta config I was trouble shooting before but has slight changes. I will upload another config when I get it to crash as well.

just bizzare.

[vortex222]

crash and logs

[Toni Wilen]

For some reason I can't match the dump file with winuae.exe/pdb files. Is it possible your winuae.exe is not official beta? (winuae.7z are development versions that can't be used debug crash dumps)

Does later betas also crash?

[vortex222]

This was an EXE you linked for me to fix a problem with the RTG screen swapping corruption. Something on my end must have changed for it to start crashing as it was really working well for a while. It also crashes with a cdtv and cd32 configuration where I added fastram and hardrive. Though the CD32 has a somewhat weird ram setup due to the FMV board being selected as well.

here is a crash with beta7 from may 4. Pardon the zip file, the one log was past the 100k limit.

[vortex222]

That log file has a huge string of "illegal lget" messages when i right clicked to open magic menu. it didn't do that a second time. I am going to investigate what setups i have common between the different profiles to see if i am setting something up that it doesnt like.

[vortex222]

So as of yet I am unable to make another machine crash that seemed to crash prolifically on beta 4. Usually within a few minutes of use. However this machine doesn't have magic menu or better workbench. And runs 3.2.1. not really any software in common at all.

[Toni Wilen]

b7 dump worked. It crashes because input configuration has become corrupted. Reason currently unknown. I don't think this is input related directly because your input config is nothing special and there are no on the fly input device changes either.

lget errors should affect emulator (no JIT enabled) but some Amiga side program is clearly doing bad memory accesses.

These two also happening during boot:

57-285 [122 025-090]: Illegal lget at 80200272 PC=21ea3c
57-286 [122 122-091]: Illegal lget at 8020024e PC=21ea3c

It also crashes with a cdtv and cd32 configuration where I added fastram and hardrive. Though the CD32 has a somewhat weird ram setup due to the FMV board being selected as well.

This might be different. Could you also attach dump (using b7)
Does it only happen if also harddrive is in use? If yes, does it still happen if you only boot without startup-sequence? (This would rule out some Amiga program doing something really weird)

[vortex222]

Strangely the only configuration on B7 i have had a crash from is that one config. I don't have the 386 bridgeboard software loaded yet, but as I have been trying to see what crashes, playing with ram configs and Switching to uaegfx still crashes... removing the bridgeboard isa devices one at a time. Though the 386 bridge board is still enabled.

The only thing that seemed to make a difference was when i removed the bridgeboard mouse, I have sofar gotten about 45 minutes without a crash. But I have not used it longer than that at this point. It usually crashes anywhere from 5 minutes to an hour.

As to what triggered the crashes, it seems random. Sometimes just from opening a drawer, or sometimes clicking the bottom statusbar config button to bring up the UI, to sometimes just leaving it sit. Most of them have come while installing a program from adf's.. But given the short time to crash and the length of time installing programs can take, I didn't think that would be significant.

Another thought I had was the A2k P96 config is one I have had a very long time through lots of versions of the software,(probably 10 years) while the cd32 and cdtv configs were quite new and made on B4 a week or two ago. Though briefly comparing it to other configs with Notepad++ didn't show any obvious differences or residual options...

Another config that crashed on B4 was an A1200 that was pretty basic however also quite old. But with about 4 hours of continuous use on it with B7 this morning I had no crash from it. I will keep playing around.

Forgive the rambling, I am just thinking through my keyboard.. No other thoughts come to mind though for now.

[vortex222]

I just made it. it crashed as i was trying to change a cdrom drive assignment and clicked ok..

[Toni Wilen]

Originally Posted by vortex222

Strangely the only configuration on B7 i have had a crash from is that one config. I don't have the 386 bridgeboard software loaded yet, but as I have been trying to see what crashes, playing with ram configs and Switching to uaegfx still crashes... removing the bridgeboard isa devices one at a time. Though the 386 bridge board is still enabled.

The only thing that seemed to make a difference was when i removed the bridgeboard mouse, I have sofar gotten about 45 minutes without a crash. But I have not used it longer than that at this point. It usually crashes anywhere from 5 minutes to an hour.

As to what triggered the crashes, it seems random. Sometimes just from opening a drawer, or sometimes clicking the bottom statusbar config button to bring up the UI, to sometimes just leaving it sit. Most of them have come while installing a program from adf's.. But given the short time to crash and the length of time installing programs can take, I didn't think that would be significant.

Another thought I had was the A2k P96 config is one I have had a very long time through lots of versions of the software,(probably 10 years) while the cd32 and cdtv configs were quite new and made on B4 a week or two ago. Though briefly comparing it to other configs with Notepad++ didn't show any obvious differences or residual options...

Another config that crashed on B4 was an A1200 that was pretty basic however also quite old. But with about 4 hours of continuous use on it with B7 this morning I had no crash from it. I will keep playing around.

Forgive the rambling, I am just thinking through my keyboard.. No other thoughts come to mind though for now.

Only way to debug this is to remove expansions until it stops crashing. This crash is also annoying because when the corruption happens, it does not necessary cause anything visible until input config is validated (to check if devices got hot inserted or removed etc) and that only happens when config change is detected, GUI is entered etc. And at this point it is far too late.

(also, don't do config changes that require removel or addition of some hardware expansion that is not removable in real world when emulation is running. It is not always reliable, better quit the emulation and rerun it)

Originally Posted by vortex222

I just made it. it crashed as i was trying to change a cdrom drive assignment and clicked ok..

Did you change something when emulation was already running and then clicked reset button? That is not always reliable. Checking the dump it looks like PCMCIA device was changed?

[vortex222]

Yeah that makes a lot of sense, this crash was during a config change. I will just have to be mindful of that. And see if i get one after properly starting emulation. I guess its not unlike those rare instances on real hardware where ctrl+AA isn't enough to resolve an issue and a full power cycle is needed.