winuae 4.9.1 crash audio .log (OS4.1FE)

[White]

Here is the .log I hope it is the useful one

Otherwise tell me exactly what it takes
Thank you.

[White]

this is the winuae 3.6.0 .log with the same configuration and it doesn't crash and works perfectly.

[Toni Wilen]

Do you mean your report in 4.9.2 thread is not 4.9.2 specific but does happen with 4.9.1 (and probably 4.9.0, check also 4.4.0 if possible) too?

If yes, I'll move related posts from beta thread.

[White]

Toni,
I wanted to ask you for advice,
It is preferable to completely restart Windows 10 at each test
to free the audio resource.
Or is it also okay in the same session and just re-launch winuae?
What is better,

Because I noticed differences if I use winuae in the same session (exiting winuae) and then relaunching it.
Instead, restarting windows 10 completely changes the tests
What is better ?

Thanks.

[Toni Wilen]

If you need to restart windows, then your audio driver or some other driver is broken.

(you didn't answer my previous post)

[White]

Toni,
Well thanks for the reply,
today I will carry out the tests
to answer your question I have already carried out the tests in reality
all versions currently appear to be affected.
But before posting the .log I was waiting for your answer.

To proceed correctly.

But before giving you the .logs I prefer to do them as precisely as possible.

[White]

Sorry deleted I have to explain myself better so it is not clear

[AMIGASYSTEM]

Ciao Paolo, I don't know I really understand your problem, but be careful, on OS3 if you disable Audio emulation on WinUAE, everything will work for the best, except programs that don't use AHI, these programs either crash like DeliTracker2 or they work but without audio see Eagleplayer.

On OS4 if you disable Audio emulation on WinUAE, no sound will be available.


---- Italiano ----


Ciao Paolo, non so so ho capito bene il tuo problema, ma attenzione, su OS3 se tu disabiliti l'emulazione Audio su WinUAE, tutto funzionerà per il meglio, eccetto i programmi che non utilizzano AHI, questi programmi o si bloccano tipo DeliTracker2 oppure funzionano ma senza audio vedi Eagleplayer.

Su OS4 se disabiliti l'emulazione Audio su WinUAE, nessun suono sarà disponibile.

[White]

@AMIGASYSTEM
Probably once again,
I can't explain myself.

Now the crash doesn't report any reports it just hangs (OS4.1).

This is not important because winuae works well with 68k
In all of my posts I have never talked about 68k because it just works perfectly.

And I have no reason to report anything.
And if I see some sprites out of place for me it's not a bug I just ignore it.

But if we talk about intensive use of OS4.1 then the problem occurs in conjunction with the audio.

The example is simple all versions of winuae work with 4.1 since PPC emulation was introduced.

But if in some cases the audio does not work and freezes winuae this would not matter.
Just quit winuae and that's it.

The main problem is this winuae not only blocks emulation (and this is not important)
but it blocks the entire windows 10 system making it impossible to close winuae if used in full screen, for example with the classic CTRL + ALT + DEL.

The only version of winuae not affected by this problem is version 3.6.0 which does this:
ALSO BLOCKS 3.6.0 but just close the application inside OS4.1 and it just doesn't completely block Windows 10 completely.

The reasons ?

Do not know them :-)

For the rest, that's okay.
I use many emulations including "PS3" "Nintendo" including the latest "Xenoblade Chronicle 3" none of these emulations completely crash Windows 10

An example for me is completely disabling audio in OS 4.1 and seeing if these crashes still occur.

If Toni feels this can somehow help her understand why Windows 10 crashes completely then .logs may be important.

Disabling the sound is just one way to see if these crashes still occur.

But before doing the .log I'm trying both G-Rex and Mediator because in reality Toni's answer has always been if it's OS4 I don't care,
But from how he wrote Toni if ??I understand correctly if I do the .log he will give it a look.
Then if I misunderstood it is useless that I start making .logs

Especially today when I have completed all the equipment of
"Lightning Javazon Amazon" and I have to redo the build (Diablo II: Resurrected).

Ok that's it

[AMIGASYSTEM]

Originally Posted by White

The main problem is this winuae not only blocks emulation (and this is not important)
but it blocks the entire windows 10 system making it impossible to close winuae if used in full screen, for example with the classic CTRL + ALT + DEL.
Resurrected).

Ok that's it

This on my Win10 32Bit does not happen, I can exit WinUAE at any time by clicking on the X, even with Win7 32Bit this does not happen.

With the new WinUAE, try creating an ex-new OS4 configuration, then maybe also try disabling the PC's Sound Card to see if the culprit is the Sound Card.

--- Italiano ---

Questo sul mio Win10 32Bit non succede, posso uscire da WinUAE in qualsiasi momento cliccando sulla X, anche con Win7 32Bit questo non succede.

Con il nuovo WinUAE, prova a creare una configurazione ex-novo di OS4, poi magari prova anche a disabilitare la Scheda Audio del PC per verificare che il colpevole sia la Scheda Audio.

[Toni Wilen]

One way to debug this is to run it in windowed mode, make it hang, windows task manager -> right click winuae.exe -> select create dump file. Compress the file (It can be very big, don't use zip but 7zip or rar or other that uses modern compression algorithm to keep it as small as possible), attach (if it is not too big) or upload it in some cloud share.

[White]

@all
All the tests I am doing now are based on 32bit

for example this does not happen with fs-uae (OS 4.1) and yet it works perfectly as I have shown in some videos posted some time ago '

trying streaming, e-uae emulator, emotion player, amigaamp, etc.

(i have no idea fs-uae 3.2 which version is compared to winuae).
however, using linux as host, taking into account that the emulated audio devices are different from winuae and also other devices.

But from my tests carried out using a usb-stick therefore very independent, winuae always remains faster for the 4.1 comparing them also with PicassoIV, winuae is simply faster.

@Toni,

Thank you,
I will do extensive tests with the various peripherals before providing you with the .logs
I don't lack patience to make them.

[White]

I leave only a small non-definitive note.
selecting uaesnd z2 as the audio device
therefore directly excluding sb128 or fm801 from the peripheral expansions
and then within OS 4.1 i choose paula stereo ++
saving the settings in OS 4.1

(note that if instead I "test" paula stereo ++ the system crashes)

but if I save directly on reboot everything works perfectly.
and leaving active for example g-rex
the crash no longer occurs with any version of winuae in general
and "ALL" applications that use audio work. (streaming playervideo e-uae audioplayer ecc.

at least I understand that it is the audio that creates the problem.
and I can test on this.

I clearly don't know the real benefits with sb128 support
winuae side.

I wrote it so I don't forget :-)
I hope it doesn't bother :-)

indeed the opposite has occurred a few times winuae 3.6.0
crashes leaving me the .dump

from version 3.6.1 onwards the crash never occurs with uaesnd z2

here dump uaesnd z2 winuae 3.6.0

[Toni Wilen]

I don't really care if some old version crashes and later ones don't.

Note that uaesnd does not have any drivers. (It happens someday maybe). Don't enable it.

[White]

Toni,
I'm sorry but in this period, I'm doing other things.
I am sure that with your preparation in programming "winuae" in the future if you find a "bug" you will easily fix it with the right .log and debug.

I have left the speech pending for the moment precisely because of the commitments I currently have.

uaesnd-z2 was an approach to the audio problem on my part to isolate the various audio tests I performed.

But I have to contradict you, certainly not because I want to do it so much to do, but because if I use winuae 3.6.0 with sb128 it is the only version that does not completely block windows 10.
Instead, all later versions instead block Windows 10 completely if I use the "drivers" like sb128.
(clearly not always but this occurs from time to time)
(this never happens with winuae 3.6.0)
But as I said above as soon as I have time I will do the various tests.

As always, thank you for your availability and your work for winuae.
as soon as I get the chance I will resume the thread of the post.
To provide you with more accurate data.


I was doing this test if I select uaesnd-z2 and sb128 at the same time and select sb128 in "AHI" so in fact "I use sb128 and not uaesnd-z2" the crash seems not to happen in later versions of winuae 3.6.0.
But only if "uaesnd-z2" is selected in the audio preferences together with "sb128" in winuae.
Actually then in OS4 I use ouch "sb128" and this seems not to block windows 10

But just as I told you in the next few days I will dedicate myself to these tests I would not want that in some way uaesnd-z2 interfere with sb128 in some way it is precisely by blocking the audio resource even by not selecting it and perhaps in builds subsequent to 3.6.0 this has remained in suspended in some way in the code implemented later.

[White]

I wouldn't want to be wrong I have to try version "winuae 3.2.0" it seems to me that in that version a bugfix has been inserted for sb128