Print

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

[DoubtingThomas]

MediaCenter 24.034 works fine (all versions past 24.034 have the issue described below.) 

However once I loaded 24.037 and 24.045 (from 24.034) (which updated Chromium), anytime I close MediaCenter or most times when I select a playlist I get a dialog that says:

https://www.dropbox.com/s/sc9z3oguvu11brm/JRiverWebAppStopped.jpg?dl=0

JRiver Web Application has stopped working.
A problem caused the program to stop working correctly, Please close the program.

with a button to "Close the program".

If the dialog shows up when selecting a playlist, I can simply close the dialog without clicking "Close the program" and MediaCenter continues to function.

Reverting to 034 gets Chromium again and then I no longer have this problem.

Jim had previously told me I needed to run the WebServer on windows startup so "Panel" can work without the MediaCenter app running.  I will never use Panel, so why should I need the WebServer running 24/7?

If starting with 037 the WebServer is required, why is there an option to not start it on Windows startup?

Since this change/problem/bug started with 037 and 034 is good, then obviously something changed in MediaCenter between 034 and 037.  Was this change intended?  If yes:

• Why?
• Shouldn't the startup option to allow not starting the WebServer be removed?
• Where is this change documented?
• Please don't force us to run the WebServer.

[JimH]

You're reporting errors with previous builds.  Please try build 45.

[DoubtingThomas]

You're reporting errors with previous builds.  Please try build 45.

Sorry I did not make that clear, I have loaded 045 today and the problem remains.

[Hendrik]

This has nothing to do with a Web Server, thats just the process that runs Chromium. But you seem to be the only one seeing this issue, so I'm not sure whats going on.
Do web views otherwise work?

[DoubtingThomas]

This has nothing to do with a Web Server, thats just the process that runs Chromium. But you seem to be the only one seeing this issue, so I'm not sure whats going on.
Do web views otherwise work?

I have never tried that, and I don't know how to do it.  I use MC for audio only.

I suspect that some code check for the WebServer is being called in new places since 24.034.

[Hendrik]

Well you must be opening some view in Media Center that opens a website, otherwise it would not even launch the web process. The start page perhaps?
On that note, if you don't conciously use any web views in Media Center, I would suggest to simply switch the web engine back to Internet Explorer and just avoid the problem that way?

[DoubtingThomas]

Well you must be opening some view in Media Center that opens a website, otherwise it would not even launch the web process. The start page perhaps?
On that note, if you don't conciously use any web views in Media Center, I would suggest to simply switch the web engine back to Internet Explorer and just avoid the problem that way?

I start MediaCenter and it automatically starts playback.  If I then exit MC, I get the "JRiver Web Application has stopped working" dialog.  I have not done anything to display any web page.  I also get the error message when simply selecting a playlist.  I have never even seen any web page displayed in MediaCenter the way I have it configured.

I could try switching the web engine to Internet Explorer, but that will not explain the change in how MC operates after 034, something obviously changed, since I can go from 034 (no problem) to 045 (problem).

I suspect that some code check for the WebServer is being called in new places since 24.034 unrelated to trying to use the WebServer.

[DoubtingThomas]

Where would I change from Chromium to Explorer in options?

[Hendrik]

Options -> Tree & View -> Web Browser -> Engine

[DoubtingThomas]

Switching to Explorer has stopped the "JRiver Web Application has stopped working" dialog.

Still I hope you are looking for what changed after 034 (good) to the later versions.

Would my log help?  Where would I send the log file?

[DoubtingThomas]

I consider switching from Chromium to Explorer a temporary solution, a work around.

Something DID change in the MC code to cause this issue on any version > 034.

I can go back and forth from 034 to 045 and the problem is not present with 034 and is present with 051.

[Awesome Donkey]

I consider switching from Chromium to Explorer a temporary solution, a work around.

If you use MC for audio only and don't use any of the web pages/views, IMO, it would be considered a fix. As for the why it happens, perhaps antivirus?

[DoubtingThomas]

If you use MC for audio only and don't use any of the web pages/views, IMO, it would be considered a fix. As for the why it happens, perhaps antivirus?

Again... the problem is NOT present with 037 and IS present with any MC version > 037, therefore it is logical to conclude that something changed in the MediaCenter code.

As I stated above, I can go back and forth between 037 and 045 and no problem with 037 and problem with 045.

I don't know why the logic of this issue is so hard and the logical fact that something has changed in the MC code or how MC interacts with Chromium.

[JimH]

Antivirus software can definitely behave with one build of MC and not with another.  Uninstall it to rule it out.

[DoubtingThomas]

Antivirus software can definitely behave with one build of MC and not with another.  Uninstall it to rule it out.

I'm using Windows Defender and has far as i know, it cannot be uninstalled.  I have disabled it, no change in the reported issue.

To rule it out, maybe the MediaCenter developers could look at why MC is now (>034) checking for the "JRiver Web Application" being active (when it's clearly not activated in options) when shutting down MC and when changing playlists?  Something in MC is triggering that error message, why is it not being triggered in 034 and is being triggered in all versions > 034?

I spent 30 years as a software developer, and when I got a trouble report after a release I would immediately look at what may have changed in our code, instead of immediately and always blaming the client's computer.  Why alienate long term paying customers? (since 2002, 16 years)

Jim, the last time you and I discussed a problem with a build was about the flickering MediaCenter screen on track change.  Around and around we went with you claiming nothing has changed in the MC code.  And a few public builds later, it was fixed.

[Awesome Donkey]

Well, disabling it might not be enough either. Windows Defender in Windows 10 is pretty integrated within the system.

Fortunately, Windows Defender can be tamed with MC24: https://yabb.jriver.com/interact/index.php/topic,115573.html

Try giving that a go, especially with excluding JRWeb.exe. I've tried to reproduce this issue, but I'm unable too. Chromium was updated and tweaked in 24.0.35 and 24.0.36 but it *shouldn't* crash unless something on the system was messing with it (or false positive flagging it). Typically if a component like that is updated, AVs (including Defender) *can* give off false positives because it's "new".

[DoubtingThomas]

Well, disabling it might not be enough either. Windows Defender in Windows 10 is pretty integrated within the system.

Fortunately, Windows Defender can be tamed with MC24: https://yabb.jriver.com/interact/index.php/topic,115573.html

Try giving that a go, especially with excluding JRWeb.exe. I've tried to reproduce this issue, but I'm unable too. Chromium was updated and tweaked in 24.0.35 and 24.0.36 but it *shouldn't* crash unless something on the system was messing with it (or false positive flagging it). Typically if a component like that is updated, AVs (including Defender) *can* give off false positives because it's "new".

I have excluded all the folders, any file inside those folders is automatically excluded too, no need to exclude individual files.

With the MediaServer disabled in Options, please explain why MC is checking for it being active when closing MC or changing playlists in MC?

If it were my app, I'd go see what code is triggering the "JRiver Web Application has stopped working" dialog and work back from there.  That is standard troubleshooting.

[Hendrik]

MC does no "checking". Like I said above, it uses that process to host the web browser control which is used in various parts of the MC UI to show web content embedded into the UI itself. It has absolutely nothing to do with Media Server.
When you change the view in MC, or close MC, the web control is unloaded and the JRWeb process closes. Apparently your Windows decides that something went wrong somewhere, and shows that Dialog (its from Windows, not MC), but doesn't say what.

So far no other user has reported such an issue, nevermind a developer seeing it to actually investigate what might be happening. Chromium works just fine here. And it is quite common for AV software to interfere with these things, especially with the Chromium component, since it contains a lot of "suspicious" things, being a web browser and all that.

[DoubtingThomas]

For now, I give up, I have reverted to 24.034 and MC works okay for me (audio only).

I will check back in a month or so to see if the issue is fixed, if not, it's the end of an era for me with MediaCenter (16 years).

I've been through this before so many times, I report an issue, my PC is blamed, antivirus is blamed... and a few releases later the issue is magically fixed.  Hopefully history will repeat itself again.

[Hendrik]

I really don't understand your attitude. You say you don't actively use any advanced web function in MC. And switching the web engine to IE fixes it (which is the default, by the way). So what exactly is the problem that remains for you?