I don't think the profiler is loading an old build since I hard reloaded the browser and also disabled catching in Network tab in devtools. I can give wasm-dis or wasm2wat a try.
On Thursday, 2 April 2020 16:29:29 UTC+5:30, Amit Gupta wrote: > > I am trying to profile my wasm build on Chrome using JavaScript Profiler. > The code itself is working fine. When I record a snapshot of page load and > analyse it, all the function names are coming to be <wasm-unnamed>. This is > happening 90% of times. 1-2 times, it worked fine. This is > causing ambiguous behaviour. I am using 1.38.28 version of emsdk and Chrome > version is Version 80.0.3987.162 (Official Build) (64-bit). Can someone > suggest what is happening here? Same issue is happening on Chrome Canary > and latest Edge browser too. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/2170aae6-1cbf-40a2-a829-546e94c8cfe0%40googlegroups.com.
