WACUP

Preview Build Discussion => Preview Build Discussion => Topic started by: PimpUigi on June 06, 2020, 12:56:25 AM

Title: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on June 06, 2020, 12:56:25 AM
Do I need to upload any dumps or anything? I have tried all the different sound output plugins, crashes as soon as I play a file.
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on June 06, 2020, 01:17:37 AM
If you've posted this a few minutes after experiencing the crashes then a quick workaround should be to disable the library history play tracking (preferences -> media library -> history -> top option).

Oddly enough I spent a large part of the previous week re-working the history tracking to resolve odd issues it's been having though I was hoping to wait another week or 2 before I push out an update (I've not yet updated to the newer Win10 revision to be able to self test it yet).

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on June 06, 2020, 01:37:04 AM
Stellar service Dr.O!
I imagine all the crashes I was having today were sending you reports huh?
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: Aminifu on June 06, 2020, 04:16:54 AM
Hi PimpUigi,

Check the selected output device for the output plug-in you're using. I updated to Windows 10 2004 on May 31 and had the same issue until I checked the output device and saw it had been changed to Primary Sound Driver instead of the device I need to use on my system. Major Windows 10 updates like 2004 always changes the selected output device on my system for some unknown reason.
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on June 06, 2020, 05:47:53 AM
Tbh I think it's mostly unfortunate timing as the history crash has been cropping up for a number of others but some setups have shown a spike in it across a number of output plug-ins being used. Though is a reasonable thing to check after a Windows update as some drivers seem to be re-installed as part of the process whilst others don't (never seen it happen directly on my setups but have seen it occur on others).

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on July 29, 2020, 01:17:10 PM
Been encountering this issue for a number of weeks now. : (
Was hoping the recent update would fix it but unfortunately it did not.
It doesn't happen right away, but after a number of hours. Also the seconds displayed on the track are not an indication of when Wacup will freeze. That could be any number between 2 and 1:20:02

I use a script to play a playlist every two hours, and it seems to give this message every time the script runs *after* Wacup is frozen. So it could go two days without a freeze, but then I could come back to the computer and have five or more of these error windows on top of each other.
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on July 29, 2020, 02:03:33 PM
What exactly is the script doing & does the hung instance generate a crash report eventually?

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on July 29, 2020, 03:02:14 PM
This is the bat file exactly.
"C:\Program Files (x86)\WACUP\wacup.exe" "C:\Edcast\Playlist.m3u8"

Where do I check to see if a log (or crash report) is generated? I am unsure, but if it's a file on the computer, I can post it here the next time this happens.
I think it did send a crash report about ten minutes before my post.
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on July 29, 2020, 03:33:32 PM
If there's been any crash reports generated by WACUP itself then there's a link from Preferences -> Advanced -> Error Reporting that'll just open to the folder (if applicable).

Though as it's a command-line action then that's not something I support at the moment due to how the WACUP loader & the original Winamp process have to interact which can cause odd failures at the moment.

I'm intending to start on replacing all of that code to be WACUP managed as part of August's work tasks.

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on July 29, 2020, 03:57:29 PM
It *was* pointing to winamp.exe but I thought that might be the issue, and it doesn't seem like it "at the moment" but as it happens sporadically it's hard to track what might be the cause.

I will be in touch as the issue progresses. I appreciate all of your hard work and continue devotion to this wonderful program. It is a life saver.

[edit - dro]
have grabbed the crash report & now removed the file from the post
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on July 29, 2020, 04:27:13 PM
Just had a look at the crash report (I had received it earlier) & it appears to be a dsp_edcast caused issue (not sure if it's directly the cause or it locking up is the end result of other things).

I assume you're using dsp_edcast because you're connecting to an icecast server or is it due to a missing format that WACUP's streaming mode doesn't support?

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on July 30, 2020, 01:32:29 AM
I used to broadcast to icecast servers, but recently have not had to.
Mostly I've been using it the last couple years because I know how it works, and so that's "easy" - is there something that you'd recommend?

When I try to use the Streaming Source beta, it crashes Wacup when I click connect. (the other station uses a live Line In broadcast, and not mp3 file broadcasts. So edcast suits that one still.)
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on July 30, 2020, 01:45:21 AM
Tried with and without a DJ name. Unsure of what to do next.
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on July 30, 2020, 02:22:50 AM
I'm assuming most of the crash reports within the last hour or so is from you. I'll look over them tomorrow & update on what to do as it really shouldn't be crashing just from trying to connect as seems to be the case from your screenshot.

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on July 30, 2020, 05:32:49 PM
I've never seen it behave like it's doing in your crash reports as it seems to have failed to initialise a number of key internal aspects & that's then causing it to enter a locked state. I'll see if there's anything I can do for the next build though not sure what at the moment as I'm a bit stumped.

Was there anything specific that you were doing as I couldn't help notice that the instances showed as having been running for a few minutes before the failure. Just trying to find out if there's anything specifically I need to be doing &/or that I'm missing in order to replicate it.

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on July 30, 2020, 09:51:07 PM
The only things I were doing was double checking the Nexuscast stream info. Making sure the ip, port number, address, and title were all typed right. Perhaps it's because Edcast dll's are in the directory or something. I will try a clean install (though retaining my Winamp.ini because I don't remember everything I've set by any means)

OK, still crashed, roughly at the same time as this Modify Post timestamp.
Crashed again with a clean winamp.ini just to be thorough. So now I'm out of ideas. : (
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on July 30, 2020, 11:28:05 PM
Looking a bit closer I've just noticed it's not using the lame_enc.dll that WACUP requires & is instead using one from 2003 found in the C:\WINDOWS\SYSTEM32 folder. So that'll explain it going all weird & I'll need to add some extra checks to avoid using non-WACUP builds of that dll.

Other than removing the old lame_enc in the system directory (assuming that was only an edcast 'addition') to hopefully allow the wacup version to be used, it'll need a newer build of the plug-in to be able to do as I note above.

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on July 30, 2020, 11:47:39 PM
Will the AAC encoding method work to let people listen from their iPhones via Safari, or Android from Chrome?
If so I'll just switch to the AAC encoder. It doesn't crash.
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on July 30, 2020, 11:59:55 PM
Dunno about iphone/safari but android/chrome should work from my prior testing.

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on July 31, 2020, 12:23:47 AM
Our listeners are reporting it's working. Thank you so much for helping with me navigate these issues!
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on July 31, 2020, 12:56:23 AM
That's useful for me to know it's ok for iphones & hopefully that should be more stable :)

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on August 02, 2020, 01:04:58 AM
Seems like it was frozen and just sent a crash report a minute ago.
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on August 02, 2020, 02:03:49 AM
Can you try changing to use the Not So Direct output plug-in as it locked up somewhere in the 5.666 DirectSound output plug-in.

At least it shows it wasn't anything like an obvious resource / memory leak for the just over 2 days it had been running.

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on August 03, 2020, 01:20:31 PM
It crashed again last night, I was too tired at the time to post. Up and running for 7 hours and 40 minutes now without issue. I don't think it sent a crash report either, next time I will make sure it does.
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on August 03, 2020, 05:11:32 PM
Had you changed the output plug-in being used?

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on August 03, 2020, 06:26:56 PM
Yeah, this is the way the window looks when I open the prefs.
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on August 03, 2020, 06:31:54 PM
Rightio, just wanted to be sure :)

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on August 13, 2020, 11:27:14 PM
Just had Wacup crash on me after at least four days of uptime. I think a crash report sent this time. Just letting you know, hoping it helps with research into why.
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on August 14, 2020, 03:23:44 PM
According to the crash report, it was running for a bit longer than that ;)
Quote
WACUP process running time: 9 days + 21:47:09
It seems it got into a weird state with the output plug-in being queried for information whilst another request was in-progress. There's also something indicating maybe the audio driver failed but I'm not sure if that was due to the lock-up or the lock-up was due to it. I'll try & make some changes to hopefully better deal with what I'm seeing in the crash report.

Still almost 10 days is good going compared to how it had been :D

-dro
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: PimpUigi on August 16, 2020, 02:21:57 PM
I'm glad that info was in there. It did feel like it was a more manageable uptime. : )
Perhaps I'll look for an updated audio driver if one exists.
Title: Re: Playing a file is crashing WACUP after my update to Windows 10 2004
Post by: dro on August 16, 2020, 10:16:02 PM
I've got a change coming in the next build which should reduce the chance of what caused it without it breaking anything new (am trying to get the current output time once & cache it instead of querying it every time it's needed which has been coming up in some other crash reports so a change was needed).

The driver aspect seems to have been due to the OS trying to close the hung process & how it was reacting so that's looking much less likely a problem to follow-up on.

-dro