v5: ACCESS_VIOLATION - The resource loader failed to find MUI file

Options
OldPilgrim
edited August 2020 in Photon Server
My server crashed in the middle of the night with the following log output
220: 02:33:42.777 - Custom crash dump created: C:\Users\Me\Photon-OnPremises-Server-Plugin-SDK_v5-0-1-21359-BETA\deploy\bin_Win64\log\PhotonSocketServer.exe-[5-0-1-6397]-20200811-023338-5048-220-2.dmp"
3668: 02:33:42.730 - Custom crash dump created: C:\Users\Me\Photon-OnPremises-Server-Plugin-SDK_v5-0-1-21359-BETA\deploy\bin_Win64\log\PhotonSocketServer.exe-[5-0-1-6397]-20200811-023323-5048-3668-1.dmp"
3668: 02:33:51.011 - Custom crash dump created: C:\Users\Me\Photon-OnPremises-Server-Plugin-SDK_v5-0-1-21359-BETA\deploy\bin_Win64\log\PhotonSocketServer.exe-[5-0-1-6397]-20200811-023342-5048-3668-3.dmp"
3668: 02:33:51.011 - JetByte.Socket.New.Stream.Socket.Connected.Internals|ERROR| S:000000000C519AE0 - ReportError CStreamSocketInternals::ProcessQueuedCommand() - CException: 0x00000001406474D0 - ACCESS_VIOLATION - E: 666
3668: 02:33:51.167 - WebSocketInSecureHost|ERROR| CTCPWebSocketServer - OnError - CStreamSocketInternals::ProcessQueuedCommand() - CException: 0x00000001406474D0 - ACCESS_VIOLATION - The resource loader failed to find MUI file.
220: 02:33:51.199 - Custom crash dump created: C:\Users\Me\Photon-OnPremises-Server-Plugin-SDK_v5-0-1-21359-BETA\deploy\bin_Win64\log\PhotonSocketServer.exe-[5-0-1-6397]-20200811-023342-5048-220-4.dmp"
220: 02:33:51.199 - JetByte.Socket.New.Stream.Socket.Connected.Internals|ERROR| S:000000000C51FB20 - ReportError CStreamSocketInternals::ProcessQueuedCommand() - CException: 0x00000001406474D0 - ACCESS_VIOLATION - E: 666
220: 02:33:51.199 - WebSocketInSecureHost|ERROR| CTCPWebSocketServer - OnError - CStreamSocketInternals::ProcessQueuedCommand() - CException: 0x00000001406474D0 - ACCESS_VIOLATION - The resource loader cache doesn't have loaded MUI entry.

When I tried to connect from the client side (Unity WebGL), the browser console logged something like "WebSocket connection to 'wss://myserver.example.com:3000/' failed: Connection closed before receiving a handshake response"

However, when I restarted the server, the clients could connect again just fine.

Any idea what's causing this? I can give you the .dmp files but they are a couple hundred MBs

Comments

  • chvetsov
    Options
    hi, @OldPilgrim

    Please send us link from where we could download this dump. Our devs will take a look

    best,
    ilya
  • OldPilgrim
    edited August 2020
    Options
    Hello @chvetsov , any progress on this? Can i delete the files yet?

    I had the same error again with the following on the client side:

    Capture.png

    However no crash was detected on the server this time. When I restarted the server service again, everything was back to normal and the client could connect again.

    Would it help if I connected to the nameserver instead of master?
  • chvetsov
    Options
    @OldPilgrim yes, you may delete

    A lot of stuff were refactored since release. So this stuff is not actual already. Thank you for your reports

    best,
    ilya
  • OldPilgrim
    Options
    @chvetsov ok, does this mean you have discovered a problem and are working on a fix, or that this issue still on your TODO list? Thank you
  • chvetsov
    Options
    @OldPilgrim
    it should be fixed by refactoring of that sub system, not just fixed

    best,
    ilya
  • OldPilgrim
    edited August 2020
    Options
    Hello @chvetsov , do you have an ETA for the next release? It is kind of not ideal deploying this in production since it crashes quite frequently
  • chvetsov
    Options
    hi, @OldPilgrim

    we are finishing some new stuff and want to test it in our cloud first before release. Once it is tested we will release new version

    so, it will take at least couple of weeks

    best,
    ilya
  • OldPilgrim
    edited August 2020
    Options
    Ok @chvetsov thank you.

    I want to add that even when the WebSocket client fails to connect, it is possible to still connect to the server via UDP. So the problem is specifically with WebSocket(Secure). It seems to occur after a certain number of connection requests to the server.

    And to answer my own question earlier, no it does not help if I connect via the nameserver instead of directly to master.
  • 4ipideil
    Options
    we have exactly the same error, is there any hope for a fix?
  • chvetsov
    Options
    hi, @4ipideil
    yes

    best,
    ilya
  • 4ipideil
    4ipideil
    edited May 2021
    Options
    hey @chvetsov, is there any new version of the server that we are not aware then? we are using this old one from the link:
    https://www.photonengine.com/sdks#server-sdkserverserverplugin
    Version: 5.0.1.21359

    so the logs and the version are very much the same:
    3964: 22:34:40.812 - Existing dump file: PhotonSocketServer.exe-[5-0-1-6397]-20210428-131227-1808-3476-1.dmp
    3964: 22:34:40.812 - Existing dump file: PhotonSocketServer.exe-[5-0-1-6397]-20210428-131237-4012-5528-1.dmp
    3964: 22:34:40.812 - Existing dump file: PhotonSocketServer.exe-[5-0-1-6397]-20210428-131244-4976-2636-1.dmp
    3964: 22:34:40.812 - Existing dump file: PhotonSocketServer.exe-[5-0-1-6397]-20210428-131300-2208-4172-1.dmp
    3964: 22:34:40.812 - Existing dump file: PhotonSocketServer.exe-[5-0-1-6397]-20210428-131325-940-3200-1.dmp
    3964: 22:34:40.812 - Existing dump file: PhotonSocketServer.exe-[5-0-1-6397]-20210428-131343-6092-1696-1.dmp
    3964: 22:34:40.812 - Existing dump file: PhotonSocketServer.exe-[5-0-1-6397]-20210428-131512-3404-5648-1.dmp
    3964: 22:34:40.812 - Max dumps to produce reduced to 3 due to 7 existing dump files
    3964: 22:34:51.015 - Custom crash dump created: C:\Users\Administrator\Desktop\photon-server\deploy\bin_Win64\log\PhotonSocketServer.exe-[5-0-1-6397]-20210503-223440-4076-3964-1.dmp"
    3964: 22:34:53.854 - Custom crash dump created: C:\Users\Administrator\Desktop\photon-server\deploy\bin_Win64\log\PhotonSocketServer.exe-[5-0-1-6397]-20210503-223451-4076-3964-2.dmp"
    3964: 22:34:53.854 - JetByte.Socket.New.Stream.Socket.Connected.Internals|ERROR| S:000000000E73EBA0 - ReportError CStreamSocketInternals::ProcessQueuedCommand() - CException: 0x00000001406474D0 - ACCESS_VIOLATION - E: 666
    3964: 22:34:53.854 - WebSocketInSecureHost|ERROR| CTCPWebSocketServer - OnError - CStreamSocketInternals::ProcessQueuedCommand() - CException: 0x00000001406474D0 - ACCESS_VIOLATION - The resource loader failed to find MUI file.
    3964: 22:41:03.779 - Custom crash dump created: C:\Users\Administrator\Desktop\photon-server\deploy\bin_Win64\log\PhotonSocketServer.exe-[5-0-1-6397]-20210503-224103-4076-3964-3.dmp"
    3964: 22:41:03.779 - Did not create crash dump. Already created: 10 and 7 already existed
    3964: 22:41:03.779 - JetByte.Socket.New.Stream.Socket.Connected.Internals|ERROR| S:000000000E73EDD0 - ReportError CStreamSocketInternals::ProcessQueuedCommand() - CException: 0x00000001406474D0 - ACCESS_VIOLATION - E: 666
    3964: 22:41:03.779 - WebSocketInSecureHost|ERROR| CTCPWebSocketServer - OnError - CStreamSocketInternals::ProcessQueuedCommand() - CException: 0x00000001406474D0 - ACCESS_VIOLATION - The resource loader cache doesn't have loaded MUI entry.
    3760: 22:47:57.592 - Did not create crash dump. Already created: 10 and 7 already existed
    3760: 22:47:57.592 - Did not create crash dump. Already created: 10 and 7 already existed
    3760: 22:47:57.592 - JetByte.Socket.New.Stream.Socket.Connected.Internals|ERROR| S:000000000E73FD20 - ReportError CStreamSocketInternals::ProcessQueuedCommand() - CException: 0x00000001406474D0 - ACCESS_VIOLATION - E: 666
    3760: 22:47:57.592 - WebSocketInSecureHost|ERROR| CTCPWebSocketServer - OnError - CStreamSocketInternals::ProcessQueuedCommand() - CException: 0x00000001406474D0 - ACCESS_VIOLATION - The resource loader cache doesn't have loaded MUI entry.
    3964: 23:10:51.737 - Did not create crash dump. Already created: 10 and 7 already existed
    3964: 23:10:51.737 - Did not create crash dump. Already created: 10 and 7 already existed
    3964: 23:10:51.737 - JetByte.Socket.New.Stream.Socket.Connected.Internals|ERROR| S:000000000E73FD20 - ReportError CStreamSocketInternals::ProcessQueuedCommand() - CException: 0x00000001406474D0 - ACCESS_VIOLATION - E: 666
    3964: 23:10:51.737 - WebSocketInSecureHost|ERROR| CTCPWebSocketServer - OnError - CStreamSocketInternals::ProcessQueuedCommand() - CException: 0x00000001406474D0 - ACCESS_VIOLATION - The resource loader cache doesn't have loaded MUI entry.
    
  • chvetsov
    Options
    there is no version yet but we do our best to release new beta soon

    best,
    ilya
  • 4ipideil
    Options
    got it! thanks!
  • JohnTube
    JohnTube ✭✭✭✭✭
    edited May 2021
    Options
    Hi @4ipideil,

    Thank you for choosing Photon!

    Photon Server v5 RC1 is out.

    Please try it out and see if it fixes this issue.