silverlight re-initialization works on chromium but crashes on firefox

Hi,

it seems like it is required to register an account to play the game above, so I cannot directly reproduce the error.
In order to find out whats going wrong, please do the following steps:

* Close all your firefox browsers
* Now open a terminal, and type: firefox &> ~/pipelight.log
* As soon as it crashes close your browser (if it doesn't crash completely), and then upload the file pipelight.log in your home directory

This file should most probably contain the reason why something is going wrong with firefox.

Sebastian

Just a small side node: The daily PPA normally isn't intended to be used by the public, as this one contains newer versions which probably might still contain bugs. The content in the daily one is generated completely automatically and its not a real release like the other one. But: concerning your specific problem this shouldn't make any difference. So you can also do this test with the daily PPA.

Here is the log.

Hi,

I don't see any real error in this log, but I can imagine that there is a difference in the way firefox handles plugin crashes.

It seems like the game consists of multiple Silverlight applications. Unfortunately Silverlight itself is full of bugs - thats why plugins often crash or have to be killed when trying to deinitialize them. On Windows most of the browsers do not even deinitialize them, because its known to be buggy.

Whereas Chrome seems to have no problems with crashing plugins, Firefox obviously reloads the page, and thats why it doesn't work anymore.

One possible workaround for this issue might be implementing a way that Firefox doesn't notice the crash - this might be possible as a future improvement to make it work better with such sites, but requires a bit more complicated solution. I have added this to the wishlist for future improvements.

Sebastian

Hi,

can you probably try out if the following workaround helps for firefox?

Open "about:config" and change the values according to:

"dom.ipc.plugins.processLaunchTimeoutSecs" = "1"
"dom.ipc.plugins.timeoutSecs" = "2"

This has been reported by other users to help in some cases.

Sebastian

Ok, now it crashes (at the same moment) and shows the page saying "silverlight plugin has crashed, reload the page to try again. No repport available".
Should I send you the log as well?

Sorry, I missed your previous message. I understand then.
There is indeed some stuff crashing under the chrome version. There is a chat box where you also have some diverse messages appearing, and when I do certain actions, I have some crash reports giving an address on the website of microsoft containing a crash report (or something like that):
http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.00&File=mscorlib.dll&Key=Arg_NullReferenceException

So as you say, maybe firefox does not like this and just reload the plugin/page.

Hi,

If the crash occurs when unloading the plugin (for example loading a new page/plugin just after logging in): this is nothing unusual, and as already mentioned above a known bug in Silverlight itself. But if the plugin crashes in the middle of playing or when doing nothing, this might be an error.

If you also have experienced the second issue (this was not the case in the previous log you have uploaded), you can try to create a new one, so I can take a look at it.

In order to check out if my previous theory (that its just firefox which doesn't like the crash and reloads the page) is correct, I will try to create an account for testing purposes (if thats possible) and check if I can reproduce this bug.

I will report back if I find out anything new.

Sebastian

Well, with changing the parameters, the only difference is that it crashes a bit sooner, and it shows the crash report page. Otherwise, if I increase the value like 100 or 200, then it last like a sec or two longer, and it reloads the page.
There is three parts to access the game. First is the login screen page (that you might have access), then you have another page where you can select your character/server and then it loads the game itself.
So basically it is crashing at the moment you are supposed to be able to have the interaction on the third part.
Maybe I can make a video record if it helps you?

Here is a video showing both chromium and firefox, before and after changing the Timeout parameters.
http://ubuntuone.com/2hMjAHNiNOunxyCbmW7kdO

Hi,

the video and also some of my tests seem to confirm, that its just because of the difference behaviour of firefox.

Can you try setting these values in about:config ?

dom.ipc.plugins.processLaunchTimeoutSecs = 10
dom.ipc.plugins.reportCrashURL = false
dom.ipc.plugins.timeoutSecs = 2
dom.ipc.processCount 3
dom.ipc.tabs.shutdownTimeoutSecs = 2

You can reset to the default values at any time if that doesn't help.

Sebastian

I tried the parameters, and the problem is the same as the parameters you previously asked me to try.

p.s.: Sorry for the long time to respond, but it was week end, and then they had pb with their server.

Hi,

could you retest fatecraft on firefox after updating pipelight? We changed some things in version 0.1-4 which may solve your issue.

Michael

Still not working. with the latest version 0.1-4.

Hi,

we recently pushed a new set of wine-patches, which should fix almost all remaining plugin deinitialization problems.
As this was the main cause for the problems on many pages, I would recommend to test again - there is no 100% guarantee though, as the feature to restart crashed plugins on-the-fly is still missing. Ensure that you're using the latest wine-compholio/wine-silverlight 1.7.3.

Sebastian

I tested with the latest wine-compholio/wine-silverlight 1.7.4 and pipelight v0.2, the problem is still there. Thanks for the update.

I have the same bp on this game (starts the game and goes back to home) with a fresh installation of Pipelight + Silverlight 5.1
Doesn't work on Firefox nor Chrome. Also tried with given FF parameters.

Pipelight 0.2.7.1~ubuntu12.04.1

Changed importance to medium. As Chrom(ium) doesn't support NPAPI anymore we will have to track down, why it doesn't work in Firefox (maybe also involves fixing bugs in Firefox itself).

Invalidating Ubuntu task
Not sure why it was even created