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.
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