Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice

Question WebGL non readable stacktrace in prod build

Discussion in 'Web' started by MrMadeoke, Jan 18, 2023.

  1. MrMadeoke

    MrMadeoke

    Joined:
    Jan 16, 2023
    Posts:
    1
    Hi, I ran into a debugging issue in a prod environment with Unity Unity 2022.1.24f1 and WebGL. When an exception occurs, I get an unreadable stacktrace. Something like this:

    Code (CSharp):
    1. Invoking error handler due to
    2. RuntimeError: unreachable
    3. at wasm://wasm/0785b666:wasm-function[985]:0x98818
    4.     at wasm://wasm/0785b666:wasm-function[544]:0x89330
    5.     at wasm://wasm/0785b666:wasm-function[8670]:0x24dccf
    6.     at wasm://wasm/0785b666:wasm-function[1922]:0xbf4e5
    7.     at wasm://wasm/0785b666:wasm-function[28368]:0x812a8b
    8.     at wasm://wasm/0785b666:wasm-function[86902]:0x14c5d3c
    9.     at wasm://wasm/0785b666:wasm-function[557]:0x898ed
    10.     at wasm://wasm/0785b666:wasm-function[77488]:0x1326327
    11.     at wasm://wasm/0785b666:wasm-function[5230]:0x171c41
    12.     at wasm://wasm/0785b666:wasm-function[10658]:0x2feb0d
    13.     at wasm://wasm/0785b666:wasm-function[104320]:0x178c493
    14.     at invoke_iiii (blob:http://localhost:8080/eef1af57-52ea-407d-b414-b8a770143494:3:408461)
    15.     at wasm://wasm/0785b666:wasm-function[2104]:0xc4fc3
    16.     at wasm://wasm/0785b666:wasm-function[24046]:0x7aace3
    17.     at wasm://wasm/0785b666:wasm-function[990]:0x989d5
    18.     at wasm://wasm/0785b666:wasm-function[21506]:0x561c30
    19.     at wasm://wasm/0785b666:wasm-function[51389]:0xd496a6
    20.     at wasm://wasm/0785b666:wasm-function[109425]:0x18f3801
    21.     at wasm://wasm/0785b666:wasm-function[108044]:0x1853d4c
    22.     at wasm://wasm/0785b666:wasm-function[23913]:0x79ec70
    23.     at wasm://wasm/0785b666:wasm-function[23913]:0x79ece1
    24.     at wasm://wasm/0785b666:wasm-function[21361]:0x554206
    25.     at wasm://wasm/0785b666:wasm-function[104316]:0x178c45d
    26.     at browserIterationFunc (blob:http://localhost:8080/eef1af57-52ea-407d-b414-b8a770143494:3:229388)
    27.     at callUserCallback (blob:http://localhost:8080/eef1af57-52ea-407d-b414-b8a770143494:3:182585)
    28.     at Object.runIter (blob:http://localhost:8080/eef1af57-52ea-407d-b414-b8a770143494:3:183845)
    29.     at Browser_mainLoop_runner (blob:http://localhost:8080/eef1af57-52ea-407d-b414-b8a770143494:3:182120)
    I can't enable debug symbols mode for prod environment, is there any algorithm to translate this stack trace to real method names?

    I found out, that Library\Bee\artifacts\WebGL\il2cppOutput\cpp\Symbols\MethodMap.tsv file has all method names from my app, but I didn't found any relations between those method names/their serial number and numbers in stacktrace.