Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lethal Company time tracker doesn't load #2502

Open
1 task
shlyakpavel opened this issue Nov 22, 2024 · 1 comment
Open
1 task

Lethal Company time tracker doesn't load #2502

shlyakpavel opened this issue Nov 22, 2024 · 1 comment
Labels
bug Something isn't working needs reduction Issue needs someone to make a minimal test case that demonstrates the problem. web compatibility

Comments

@shlyakpavel
Copy link
Contributor

Summary

When I open a time tracker in Ladybird, it shows Application exit (Wasm execution trapped (WIP): Memory access out of bounds) while loading

Operating system

macOS

Steps to reproduce

  1. Open Ladybird
  2. Navigate to https://ratijas.tk/lc/
  3. Observe

Expected behavior

Web app loads

Actual behavior

Web app not loads

URL for a reduced test case

https://ratijas.tk/lc/

HTML/SVG/etc. source for a reduced test case

N/A

Log output and (if possible) backtrace

2024-11-22 18:15:24.869 Ladybird[99584:4267125] +[IMKClient subclass]: chose IMKClient_Modern
2024-11-22 18:15:24.914 Ladybird[99584:4267125] +[IMKInputSession subclass]: chose IMKInputSession_Modern
183290.099 WebContent(99588): LibWasm: Memory access out of bounds (expected 3785438157 to be less than or equal to 52428800)
183290.100 WebContent(99588): (js error) [TypeError] Wasm execution trapped (WIP): Memory access out of bounds
183290.100 WebContent(99588): (js error) "TypeError: Wasm execution trapped (WIP): Memory access out of bounds\n    at Yh\n    at callRuntimeCallbacks (https://ratijas.tk/lc/appLethalClocksQml.js:8:9430)\n    at initRuntime (https://ratijas.tk/lc/appLethalClocksQml.js:8:4168)\n    at doRun (https://ratijas.tk/lc/appLethalClocksQml.js:8:296491)\n    at run (https://ratijas.tk/lc/appLethalClocksQml.js:8:296792)\n    at runCaller (https://ratijas.tk/lc/appLethalClocksQml.js:8:295879)\n    at removeRunDependency (https://ratijas.tk/lc/appLethalClocksQml.js:8:5154)\n    at receiveInstance (https://ratijas.tk/lc/appLethalClocksQml.js:8:7609)\n    at receiveInstantiationResult (https://ratijas.tk/lc/appLethalClocksQml.js:8:7745)\n    at <unknown>\n"

Screenshots or screen recordings

image

Build flags or config settings

No response

Contribute a patch?

  • I’ll contribute a patch for this myself.
@shlyakpavel
Copy link
Contributor Author

This seem to happen to other Qt WebAssembly apps as well, such as demos at https://www.qt.io/qt-demos#demo

@AtkinsSJ AtkinsSJ added bug Something isn't working web compatibility needs reduction Issue needs someone to make a minimal test case that demonstrates the problem. labels Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs reduction Issue needs someone to make a minimal test case that demonstrates the problem. web compatibility
Projects
None yet
Development

No branches or pull requests

2 participants