Problem with FpsHelper

[dwrainman]

A while back I had this dreaded FPSHelper error and managed to get around it by recreating my main application project.. this is pretty hoky and not reliable. Now after another update to the platform it has come back again, nothing changed except the update. This time creating a new project has not helped, (The type initializer for 'FpsHelper' threw an exception.) persists and I am STUCK!!!! I have invested too much time in UNO to chuck it in, but seriously I waste more time with UNO than I ever have dealing with sh&* that is out of my control, and I am regretting ever using it. I just want to code and make some great software, not spend time trouble shooting the platform it runs on..

Is there a support person that can help me out here????

[jeromelaban]

Thank you for your feedback.

This community does not be accept this kind of language, please make sure to read our code of conduct.

This error generally happens when .NET WebAssembly workloads are not installed, see this article about it.

If you continue having more problems, make sure to provide more logs from the browser debugger in order to help you further..

[jeromelaban]

This issue went away last time after I recreated the application project, not something that one should have to do. Then, I was fine for about a month, then it came back after doing an update of the platform. So if I haven’t removed any of the .NET webassembly workloads, why would they disappear?

A few things:

• Can you provide the actual error from the browser's debugger?
• Can you provide the full output of uno-check --verbose
• Can you provide a binlog of your app?
• Can you tell the steps you use to run your app?

Thanks.

[jeromelaban]

@dwrainman thanks for the update. Sending emails to conversations does not work well on GitHub, please make sure to use the website to post the information, thanks.

[dwrainman]

Hi Jerome As you can probably tell, I am getting very frustrated. Time and time again I have run into blockers from the platform. Getting blockers from a coding issue is one thing, getting it from the platform that you are running under is completely different. This issue went away last time after I recreated the application project, not something that one should have to do. Then, I was fine for about a month, then it came back after doing an update of the platform. So if I haven’t removed any of the .NET webassembly workloads, why would they disappear? Can you tell me how I would check which workloads are missing and how to reinstall them, I have run Uno-Check many times. Thank you for your attention to this. Apologize for my frustration. From: Jérôme Laban ***@***.***> Sent: Wednesday, 10 September 2025 9:55 PM To: unoplatform/uno ***@***.***> Cc: dwrainman ***@***.***>; Author ***@***.***> Subject: Re: [unoplatform/uno] Problem with FpsHelper (Discussion #21453) Thank you for your feedback. This community does not be accept this kind of language, please make sure to read our code of conduct <https://github.com/unoplatform/uno/blob/master/CODE_OF_CONDUCT.md> . This error generally happens when .NET WebAssembly workloads are not installed, see this article about it <https://platform.uno/docs/articles/common-issues-wasm.html#webassembly-dllimport-unable-to-load-library-libskiasharp> . If you continue having more problems, make sure to provide more logs from the browser debugger in order to help you further.. — Reply to this email directly, view it on GitHub <#21453 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6WLM6P7LYLNW7YIGGKRYN33SAGRZAVCNFSM6AAAAACGCYRWWSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZWGIYTENA> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/A6WLM6PM2IKXGYAW2QXY3WT3SAGRZA5CNFSM6AAAAACGCYRWWSWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQA3MTAY.gif> Message ID: ***@***.*** ***@***.***> >

[dwrainman]

Hi Jerome Please find attached the browser error and uno-check, I have to install some things to get the binlog. I don’t do anything unusual when I run the app, I am only outputting to windows and wasm. BTW, windows works no problem, and I suppose considering it seems faster to build and run I might just go that way and then publish to wasm. But still I would like to be able to run it under wasm. Best Regards David From: Jérôme Laban ***@***.***> Sent: Wednesday, 10 September 2025 10:46 PM To: unoplatform/uno ***@***.***> Cc: dwrainman ***@***.***>; Author ***@***.***> Subject: Re: [unoplatform/uno] Problem with FpsHelper (Discussion #21453) This issue went away last time after I recreated the application project, not something that one should have to do. Then, I was fine for about a month, then it came back after doing an update of the platform. So if I haven’t removed any of the .NET webassembly workloads, why would they disappear? A few things: * Can you provide the actual error from the browser's debugger? * Can you provide the full output of uno-check --verbose * Can you provide a binlog of your app <https://platform.uno/docs/articles/uno-builds-troubleshooting.html> ? * Can you tell the steps you use to run your app? Thanks. — Reply to this email directly, view it on GitHub <#21453 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6WLM6O22JQOHFZQTLQIAS33SAMPJAVCNFSM6AAAAACGCYRWWSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZWGI2TONI> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/A6WLM6I6E2Y3E67IG3IKRUT3SAMPJA5CNFSM6AAAAACGCYRWWSWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQA3MT46.gif> Message ID: ***@***.*** ***@***.***> > Fetch event handler is recognized as no-op. No-op fetch handler may bring overhead during navigation. Consider removing the handler if possible. uno-bootstrap.js:238 Setting DOTNET_MODIFIABLE_ASSEMBLIES=debug uno-bootstrap.js:238 Setting UNO_BOOTSTRAP_MONO_RUNTIME_MODE=Interpreter uno-bootstrap.js:238 Setting UNO_BOOTSTRAP_MONO_PROFILED_AOT=False uno-bootstrap.js:238 Setting UNO_BOOTSTRAP_LINKER_ENABLED=False uno-bootstrap.js:238 Setting UNO_BOOTSTRAP_DEBUGGER_ENABLED=True uno-bootstrap.js:238 Setting UNO_BOOTSTRAP_MONO_RUNTIME_CONFIGURATION=Release uno-bootstrap.js:238 Setting UNO_BOOTSTRAP_MONO_RUNTIME_FEATURES= uno-bootstrap.js:238 Setting UNO_BOOTSTRAP_APP_BASE=package_732babb443c088562d5938857d97e57fed98bc28 uno-bootstrap.js:238 Setting UNO_BOOTSTRAP_WEBAPP_BASE_PATH=/ logging.ts:33 MONO_WASM: The version of dotnet.runtime.js 893c2ebbd49952ca49e93298148af2d95a61a0a4 is different from the version of dotnet.js aae90fa09086a9be09dac83fa66542232c7269d8! Me @ logging.ts:33 (anonymous) @ startup.ts:415 Wc.e.preInit @ startup.ts:83 (anonymous) @ dotnet.native.9ih887ebfz.js:8 yt @ run.ts:489 logging.ts:33 MONO_WASM: The version of dotnet.native.js 893c2ebbd49952ca49e93298148af2d95a61a0a4 is different from the version of dotnet.js aae90fa09086a9be09dac83fa66542232c7269d8! Me @ logging.ts:33 (anonymous) @ startup.ts:418 Wc.e.preInit @ startup.ts:83 (anonymous) @ dotnet.native.9ih887ebfz.js:8 yt @ run.ts:489 assetsCache.ts:30 dotnet Loaded 87.30 MB resourcesThis application was built with linking (tree shaking) disabled. Published applications will be significantly smaller if you install wasm-tools workload. See also https://aka.ms/dotnet-wasm-features assetsCache.ts:34 Loaded 82.80 MB resources from cache assetsCache.ts:43 Loaded 4.51 MB resources from network uno-bootstrap.js:427 Debugging hotkey: Shift+Alt+D (when application has focus) marshal-to-js.ts:420 Uncaught (in promise) ManagedError: One or more errors occurred. (The type initializer for 'FpsHelper' threw an exception.) an @ marshal-to-js.ts:420 (anonymous) @ marshal-to-js.ts:315 (anonymous) @ marshal-to-js.ts:363 (anonymous) @ marshal-to-js.ts:341 fr @ invoke-js.ts:523 Fc @ marshal-to-js.ts:341 $func288 @ 00b5ba72:0x1f1bd $func219 @ 00b5ba72:0x1c8c7 $func210 @ 00b5ba72:0xea32 $func281 @ 00b5ba72:0x1eca1 $func317 @ 00b5ba72:0x1fe08 $func188 @ 00b5ba72:0xc5f6 $mono_background_exec @ 00b5ba72:0x480b1 e.<computed> @ cwraps.ts:334 Yo @ scheduling.ts:56 callUserCallback @ dotnet.native.9ih887ebfz.js:8 (anonymous) @ dotnet.native.9ih887ebfz.js:8 setTimeout safeSetTimeout @ dotnet.native.9ih887ebfz.js:8 Fc @ scheduling.ts:66 $func790 @ 00b5ba72:0x4804f $func288 @ 00b5ba72:0x1f1bd $func219 @ 00b5ba72:0x1c8c7 $func210 @ 00b5ba72:0xea32 $func247 @ 00b5ba72:0x1d442 $func3222 @ 00b5ba72:0xf1178 $func2545 @ 00b5ba72:0xc6ca7 $func2550 @ 00b5ba72:0xc749f $func2574 @ 00b5ba72:0xc9b66 $mono_wasm_invoke_jsexport @ 00b5ba72:0xaccb Module._mono_wasm_invoke_jsexport @ dotnet.native.9ih887ebfz.js:8 hn @ managed-exports.ts:280 (anonymous) @ managed-exports.ts:65 Pc @ run.ts:71 await in Pc mainInit @ uno-bootstrap.js:267 await in mainInit checkDone @ uno-bootstrap.js:369 processDependency @ uno-bootstrap.js:387 execCb @ require.js:5 check @ require.js:5 (anonymous) @ require.js:5 (anonymous) @ require.js:5 (anonymous) @ require.js:5 each @ require.js:5 emit @ require.js:5 check @ require.js:5 enable @ require.js:5 init @ require.js:5 a @ require.js:5 completeLoad @ require.js:5 onScriptLoad @ require.js:5 script req.createNode @ require.js:5 req.load @ require.js:5 load @ require.js:5 load @ require.js:5 fetch @ require.js:5 check @ require.js:5 enable @ require.js:5 enable @ require.js:5 (anonymous) @ require.js:5 (anonymous) @ require.js:5 each @ require.js:5 enable @ require.js:5 init @ require.js:5 (anonymous) @ require.js:5 setTimeout req.nextTick @ require.js:5 s @ require.js:5 requirejs @ require.js:5 require @ uno-bootstrap.js:412 (anonymous) @ uno-bootstrap.js:390 initializeRequire @ uno-bootstrap.js:372 RuntimeReady @ uno-bootstrap.js:213 Bootstrapper.onDotnetReady @ uno-bootstrap.js:124 (anonymous) @ startup.ts:451 (anonymous) @ startup.ts:351 Fetch event handler is recognized as no-op. No-op fetch handler may bring overhead during navigation. Consider removing the handler if possible.

Edge WebView2 Checkup...

- Found Edge WebView2 version 140.0.3485.54

.NET SDK - Workloads (9.0.300) Checkup...

SHELL: C:\Program Files\dotnet\dotnet.exe workload list --machine-readable {"installed":["android","aspire","ios","maccatalyst","maui","maui-windows","tvos","wasm-tools","wasm-tools-net8"],"updateAvailable":[{"existingManifestVersion":"35.0.92","availableUpdateManifestVersion":"35.0.101","description":".NET SDK Workload for building Android applications.","workloadId":"android"},{"existingManifestVersion":"18.5.9215","availableUpdateManifestVersion":"18.5.9219","description":".NET SDK Workload for building iOS applications.","workloadId":"ios"},{"existingManifestVersion":"18.5.9215","availableUpdateManifestVersion":"18.5.9219","description":".NET SDK Workload for building MacCatalyst applications.","workloadId":"maccatalyst"},{"existingManifestVersion":"18.5.9215","availableUpdateManifestVersion":"18.5.9219","description":".NET SDK Workload for building tvOS applications.","workloadId":"tvos"}]} SHELL: C:\Program Files\dotnet\dotnet.exe workload update --print-rollback { "microsoft.net.sdk.android": "35.0.92/9.0.100", "microsoft.net.sdk.ios": "18.5.9215/9.0.100", "microsoft.net.sdk.maccatalyst": "18.5.9215/9.0.100", "microsoft.net.sdk.macos": "15.5.9215/9.0.100", "microsoft.net.sdk.maui": "9.0.82/9.0.100", "microsoft.net.sdk.tvos": "18.5.9215/9.0.100", "microsoft.net.workload.mono.toolchain.current": "9.0.9/9.0.100", "microsoft.net.workload.emscripten.current": "9.0.9/9.0.100", "microsoft.net.workload.emscripten.net6": "9.0.9/9.0.100", "microsoft.net.workload.emscripten.net7": "9.0.9/9.0.100", "microsoft.net.workload.emscripten.net8": "9.0.9/9.0.100", "microsoft.net.workload.mono.toolchain.net6": "9.0.9/9.0.100", "microsoft.net.workload.mono.toolchain.net7": "9.0.9/9.0.100", "microsoft.net.workload.mono.toolchain.net8": "9.0.9/9.0.100", "microsoft.net.sdk.aspire": "8.2.2/8.0.100" } - Available workload: microsoft.net.sdk.android: 35.0.92 - Available workload: microsoft.net.sdk.ios: 18.5.9215 - Available workload: microsoft.net.sdk.maccatalyst: 18.5.9215 - Available workload: microsoft.net.sdk.macos: 15.5.9215 - Available workload: microsoft.net.sdk.maui: 9.0.82 - Available workload: microsoft.net.sdk.tvos: 18.5.9215 - Available workload: microsoft.net.workload.mono.toolchain.current: 9.0.9 - Available workload: microsoft.net.workload.emscripten.current: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net6: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net7: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net8: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net6: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net7: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net8: 9.0.9 - Available workload: microsoft.net.sdk.aspire: 8.2.2 - microsoft.net.sdk.android (35.0.92/9.0.100) is installed. - Available workload: microsoft.net.sdk.android: 35.0.92 - Available workload: microsoft.net.sdk.ios: 18.5.9215 - Available workload: microsoft.net.sdk.maccatalyst: 18.5.9215 - Available workload: microsoft.net.sdk.macos: 15.5.9215 - Available workload: microsoft.net.sdk.maui: 9.0.82 - Available workload: microsoft.net.sdk.tvos: 18.5.9215 - Available workload: microsoft.net.workload.mono.toolchain.current: 9.0.9 - Available workload: microsoft.net.workload.emscripten.current: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net6: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net7: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net8: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net6: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net7: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net8: 9.0.9 - Available workload: microsoft.net.sdk.aspire: 8.2.2 - microsoft.net.sdk.ios (18.5.9215/9.0.100) is installed. - Available workload: microsoft.net.sdk.android: 35.0.92 - Available workload: microsoft.net.sdk.ios: 18.5.9215 - Available workload: microsoft.net.sdk.maccatalyst: 18.5.9215 - Available workload: microsoft.net.sdk.macos: 15.5.9215 - Available workload: microsoft.net.sdk.maui: 9.0.82 - Available workload: microsoft.net.sdk.tvos: 18.5.9215 - Available workload: microsoft.net.workload.mono.toolchain.current: 9.0.9 - Available workload: microsoft.net.workload.emscripten.current: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net6: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net7: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net8: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net6: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net7: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net8: 9.0.9 - Available workload: microsoft.net.sdk.aspire: 8.2.2 - microsoft.net.sdk.maccatalyst (18.5.9215/9.0.100) is installed. - Available workload: microsoft.net.sdk.android: 35.0.92 - Available workload: microsoft.net.sdk.ios: 18.5.9215 - Available workload: microsoft.net.sdk.maccatalyst: 18.5.9215 - Available workload: microsoft.net.sdk.macos: 15.5.9215 - Available workload: microsoft.net.sdk.maui: 9.0.82 - Available workload: microsoft.net.sdk.tvos: 18.5.9215 - Available workload: microsoft.net.workload.mono.toolchain.current: 9.0.9 - Available workload: microsoft.net.workload.emscripten.current: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net6: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net7: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net8: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net6: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net7: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net8: 9.0.9 - Available workload: microsoft.net.sdk.aspire: 8.2.2 - microsoft.net.sdk.tvos (18.5.9215/9.0.100) is installed. - Available workload: microsoft.net.sdk.android: 35.0.92 - Available workload: microsoft.net.sdk.ios: 18.5.9215 - Available workload: microsoft.net.sdk.maccatalyst: 18.5.9215 - Available workload: microsoft.net.sdk.macos: 15.5.9215 - Available workload: microsoft.net.sdk.maui: 9.0.82 - Available workload: microsoft.net.sdk.tvos: 18.5.9215 - Available workload: microsoft.net.workload.mono.toolchain.current: 9.0.9 - Available workload: microsoft.net.workload.emscripten.current: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net6: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net7: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net8: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net6: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net7: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net8: 9.0.9 - Available workload: microsoft.net.sdk.aspire: 8.2.2 - microsoft.net.sdk.maui (9.0.82/9.0.100) is installed. - Available workload: microsoft.net.sdk.android: 35.0.92 - Available workload: microsoft.net.sdk.ios: 18.5.9215 - Available workload: microsoft.net.sdk.maccatalyst: 18.5.9215 - Available workload: microsoft.net.sdk.macos: 15.5.9215 - Available workload: microsoft.net.sdk.maui: 9.0.82 - Available workload: microsoft.net.sdk.tvos: 18.5.9215 - Available workload: microsoft.net.workload.mono.toolchain.current: 9.0.9 - Available workload: microsoft.net.workload.emscripten.current: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net6: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net7: 9.0.9 - Available workload: microsoft.net.workload.emscripten.net8: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net6: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net7: 9.0.9 - Available workload: microsoft.net.workload.mono.toolchain.net8: 9.0.9 - Available workload: microsoft.net.sdk.aspire: 8.2.2 - microsoft.net.workload.mono.toolchain.current (9.0.9/9.0.100) is installed.