INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Crashes (may be WDM)  (Read 1491 times)

mikeza

  • Recent member
  • *
  • Posts: 39
Crashes (may be WDM)
« on: December 16, 2014, 06:31:33 pm »

JRiver has been crashing on my computer a lot recently. The program hangs and I eventually cannot move the mouse. The task manager cannot be opened and I have to manually restart my computer (power button) to restore function. This has been happening a couple times/day so I did a fresh install and downgraded from build 48 to 47. This has not resolved the issue and it continues to crash.

It's hard to pinpoint the cause, but one that I can reproduce 90% time:
Audio is running in JRiver through a WASAPI device (playing an mp3)
I simply open Spotify (sometimes I have to play audio)
JRiver hangs/computer crashes

It's unusual I thought it was every time but it is really just the vast majority of times as I test it more.

I've taken several logs and tried to compare them to each other in Notepad++
Normal audio playing starts like so without problems:
Code: [Select]
0061828: 3592: Playback: CWASAPIPlugin::StartWASAPI: Started WASAPI: 1200 buffer blocks, 100.0000 internal buffer ms, 24 fill sleep ms
0061828: 3592: Playback: CWASAPIPlugin::StartWASAPI: Success opening device
0061828: 3592: Playback: CWASAPIPlugin::StartWASAPI: Finish (15 ms)
0061828: 3592: Playback: CWASAPIPlugin::Thread: Boosting priority
0061828: 3592: Playback: CWASAPIPlugin::Thread: Prerolling silence
0061828: 3592: Playback: CWASAPIPlugin::Thread: Starting
0061828: 3592: Playback: CWASAPIPlugin::Thread: Running feeder loop

0061828: 1920: Playback: CWASAPIPlugin::Open: Finish (31 ms)
0061844: 1396: Playback: CWaveOutBin::CreateBin: Finish (47 ms)
0061844: 1396: Playback: CMJWaveFeeder::Thread: Preparing to feed data
0061844: 4344: Playback: CWaveOutBinPlayThread::Thread: Start
0061844: 1396: Playback: CMJWaveFeeder::Thread: Memory playback: 0; Maximum play buffer bytes: 858993458; Grow by bytes: 134217728; System available bytes: 1073741823
0061844: 1396: Playback: CMJWaveFeeder::Thread: Running feeder loop
0061844: 1396: Playback: CPlayerZone::OnNewStream: Start
0061844: 1396: Playback: CPlayerZone::OnNewStream: Finish (0 ms)

Then from when I open Spotify this always occurs
Code: [Select]
0062266: 3196: Reader: CWinINetReader::DownloadFromHTTPURL: Success
0062266: 3196: Reader: CWinINetReader::DownloadFromHTTPURL: Finish (594 ms)
0062266: 3196: Reader: CWinINetReader::Thread: Finish (594 ms)
0062266: 4048: Reader: CWinINetReader::Open: Finish (594 ms)
0062282: 4048: Reader: CWinINetReader::Close: Start
0062282: 4048: Reader: CWinINetReader::Close: Finish (0 ms)

But from here, the logs vary, making it hard for me to pinpoint an error location.
Log #1
http://pastebin.com/CaNSicPa

Log #2 (an auto-import appears to start towards the end)
http://pastebin.com/USSR9B0Y

Log #3 (audio continued to play with much stuttering, but I could not Ctrl-Shift-Esc, could not move mouse, etc. unresponsive system)
http://pastebin.com/PDKugkXg

These failures also occur all the time due to other applications than Spotify (Chrome audio for example) and even when I'm not playing any audio outside of JRiver (I hit play on a song and JRiver hangs). I had no problems with old versions of JRiver. Any help would be appreciated. Full/additional logs can be provided, I know my way around computers.
Logged

mikeza

  • Recent member
  • *
  • Posts: 39
Re: Crashes (may be WDM)
« Reply #1 on: December 22, 2014, 01:38:58 pm »

Bump. This is still happening on the newest build.
Logged

CountryBumkin

  • Citizen of the Universe
  • *****
  • Posts: 3352
Re: Crashes (may be WDM)
« Reply #2 on: December 22, 2014, 02:28:01 pm »

Perhaps, for testing purposes, you could try running a version from "before" the WDM install/build (pre build .23). Maybe that test will help pin-point the cause for the developers.

These problems can be real hard to solve - especially when it works fine for 99% of the installs. So any testing you can do will certainly help finding a solution.

Good luck.
It sucks to be in the 1%  ;)
Logged
Pages: [1]   Go Up