Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mwgraves10]

On an older machine, I had been running MC25 for a long time. I'd tried upgrading to 26, and that crashed way too frequently to make it worth while. 27 came out and I said, what the heck and sprung for that upgrade. Never got it to work, and went back to 25. That computer finally died and I had read on the forums that later versions ran fine on WIN11. So I bought it. It installed okay. It launched fine and I started importing my library. It only imported about half of my folders before it crashed. I restarted MC33 and started the import again. It imported 16 songs and crashed. I restarted the computer, launched MC33, started the import and it instantly crashed. Just the click of the mouse button was enough to crash the program.

Restarted the computer. Launched MC33. Tried to play a song. It crashed on the mouse click.
Restarted the computer. Launched MC33. Tried to open Tools. It crashed on the mouse click.
Restarted the computer. Launched MC33. Clicked on the icon for my CD burner in Devices. It crashed on the mouse click.

[Richard Martin]

There are hundreds,  probably thousands, of people running JRiver MC on Windows 11 without problems.

There is something about your setup that is causing your problems and I'm sure with a bit if patience it can be fixed.

Enabling logging and then submitting a log file may help.

Giving some more details about your configuration may also be useful.

[Awesome Donkey]

If it's crashing on import, you likely have bad files. Enabling logging and reading what file(s) it was trying to import last are usually the clue to what's causing the crashes. As for the other stuff, this may be antivirus related, so if you're using Windows Defender make sure you follow the taming Windows Defender topic here: https://yabb.jriver.com/interact/index.php/topic,114101.0.html

[zybex]

If it's crashing on import, you likely have bad files. Enabling logging and reading what file(s) it was trying to import last are usually the clue to what's causing the crashes. As for the other stuff, this may be antivirus related, so if you're using Windows Defender make sure you follow the taming Windows Defender topic here: https://yabb.jriver.com/interact/index.php/topic,114101.0.html

Bad files are the most likely culprit.
That said, I can sympathize. A bad file should not crash the app, it should just flag that one and proceed. It's 2025, threads and try/catch are a thing.
Suggestion: run the import on a separate process, reporting progress with IPC; when it crashes, flag the current file and restart the import process on the next file.

[JimH]

If you're running antivirus software other than Windows, uninstall it.

Many other causes of crashes and their solutions can be found here:  https://yabb.jriver.com/interact/index.php/topic,24031.0.html

[JimH]

Bad files are the most likely culprit.
That said, I can sympathize. A bad file should not crash the app, it should just flag that one and proceed. It's 2025, threads and try/catch are a thing.
Suggestion: run the import on a separate process, reporting progress with IPC; when it crashes, flag the current file and restart the import process on the next file.

We've done what we can and it is threaded, but a crash can make it hard to do much more.  A failing drive or NAS can do a lot of damage, for example.

In this case, there are so many problems that it's possible that the hardware itself isn't reliable.

Program changes are best discussed in a different thread.

The log may show the crash and the corrupt file.