Very strange WinUAE 1.5.2 crash

[nikvest]

Hi Toni,

I have a strange but regular WinUAE crash. It happens almost every time I run WinUAE, sooner or later and I can't find a pattern for it. It crashes with a following message and it doesn't create a .dmp file at all!

Picture is attached below. Do you have any advice?

[Toni Wilen]

No idea, perhaps stack overflow (but why? perhaps some driver memory leak? Hardware specs? Including display and sound card. Include also winuaebootlog.txt, thanks)

Does it happen if you use basic A500 emulation mode? Or only if you use "high-end" RTG enabled setup?

You can run with log window open ("winuae.exe -log") and check if there is anything interesting when it crashes next time, also you can force dump file, do not close the dialog, open task manager, find winuae process, right click, select "Create Dump File" (Vista-only)

btw, Use ALT+Printscreen or Snipping Tool that comes with Vista (which should have been included in every Windows version but better late than newer I guess..) to get smaller screenshots

[nikvest]

There's a first clue - it seems to happen only in RTG mode, although I can't confirm that without more detailed testing...

Hardware specs:
Windows Vista 32-bit SP1
nVidia 8800 GT w/ Forceware 177.83 (latest official ones)
MB: Gigabyte M55S-S3
2 GB DDR3 RAM
AMD Athlon dual core 4000+

I will try to force dump file next time when it crashes, although I may not be able to do it until tonight or tomorrow morning. I will also attach winuaebootlog.txt next time it happens.

[nikvest]

All right, it crashed again... But here's the funny thing: it created a 312 MB dump file!!! I used your method and created it, but it's huge. If you know how I can lower it down I will attach it.

In the meantime, this was RTG Workbench environment transferred to AGA game environment. I attached winuaebootlog.txt.

[Toni Wilen]

Originally Posted by nikvest

All right, it crashed again... But here's the funny thing: it created a 312 MB dump file!!! I used your method and created it, but it's huge. If you know how I can lower it down I will attach it.

Try setting memory settings as small as possible. (disable Z3 and RTG if possible etc..)

[Toni Wilen]

Do you also have all "Vista reliability" patches installed? (maybe they help, maybe not..)

[nikvest]

All right, it created a dump file now but it was different kind of crash. I attached .dmp and winuaebootlog.txt. I'll see if I can reproduce original crash too.

Edit: I have all Vista patches.

[Toni Wilen]

Originally Posted by nikvest

All right, it created a dump file now but it was different kind of crash. I attached .dmp and winuaebootlog.txt. I'll see if I can reproduce original crash too.

Edit: I have all Vista patches.

This is crash dump I have seen few times already (mostly from dumps collected by Cloanto) but never managed to duplicate it.

Unfortunately they are mostly useless because call stack only shows 00000000(). Nothing else.. My only guess is JIT getting totally confused.

I'd expect this type of crash having some messages in winuaelog.txt.

[nikvest]

I can't access log file when original crash happens, and .dmp files created by Vista are too big no matter how little memory I assign to particular configuration. I'm gonna try to reduplicate crash with WinUAE 1.5.1.

Edit: same problem with WinUAE 1.5.1. I attached my config files, they create a crash every single time. Perhaps you could find something useful. I tried to run Virtual Ball Fighters game from CD, and I tried it in AGA mode. It crashes every single time no matter what I change, and crash also happens with Duke Nukem 3D and Doom II. I see a pattern here... (all games except DN3D were run in PAL mode - that means AGA mode. DN3D was run in RTG mode).

[Toni Wilen]

Originally Posted by nikvest

I can't access log file when original crash happens,

You can if you keep the log window open.

and .dmp files created by Vista are too big no matter how little memory I assign to particular configuration. I'm gonna try to reduplicate crash with WinUAE 1.5.1.

It should compress quite well. We will find a way to transfer it

[nikvest]

All right... Original crash, with attached winuaebootlog.txt and packed minidump file... Hope it helps.

[Toni Wilen]

Originally Posted by nikvest

All right... Original crash, with attached winuaebootlog.txt and packed minidump file... Hope it helps.

Seems to be JIT bug.

uae_u32 get_const(int r)
{
#if USE_OPTIMIZER
    if (!reg_alloc_run)
#endif
	Dif (!isconst(r)) {
	    write_log ("JIT: Register %d should be constant, but isn't\n",r);
	    abort();
	}
    return live.state[r].val;
}

(get_const() called from unsigned long REGPARAM2 op_6100_0_comp_ff(uae_u32 opcode) /* BSR */)

Odd dialog is caused by abort() function that simply instantly kills the process. (and you should see JIT: Register blahblah in the log window. Not 100% sure because it may not be flushed from the cache..)

I don't know how to fix this because I don't know JIT works (and I don't want to know..)

EDIT: probably not "real" bug but impossible condition that "shouldn't happen".

You sure it is not something silly like CPU overheating? (easy test, adjust CPU Idle setting in CPU panel)

Does it ONLY happen if you use your (custom?) WB installation? Stack overflows (too small stack), buggy patches etc.. can cause weird errors when JIT is enabled (real Amiga would just crash "normally" in this case)

[nikvest]

Give me a day or two to test different situations and I'll let you know...

Edit: You are a genius! Problem is virtual WB related. When I started the games from another WB installation (OS 3.9) problem went away. Perhaps I tried to play newer games on WB3.1 and that caused some problems which, combined with JIT caused the crash.

[nikvest]

Well, I can confirm now: problem happens only in one virtual WB install, but it is becoming more often as days go by. What can I do? Reinstall is the last resort,and I would like to try and locate a problem...

[andreas]

Originally Posted by Toni Wilen

Seems to be JIT bug.

I don't know how to fix this because I don't know JIT works (and I don't want to know..)

Maybe we can again repeat the "Miracle of Berne" and convince Bernie to fix this issue.
It could be worth a try.