Opened 5 weeks ago
Last modified 5 weeks ago
#19183 new bug
webkit: WASM high load
| Reported by: | grexe | Owned by: | pulkomandy |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Kits/Web Kit | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
This seems to happen a lot with Github pages, even with only 2-3 tabs open: WebPositive wasm-worker thread generates an increasing CPU load and eventually brings down the entire app. See screenshot. Using latest nightly as of today, hrev58241.
Attachments (1)
Change History (3)
by , 5 weeks ago
| Attachment: | webpositive-wasm-load.png added |
|---|
comment:1 by , 5 weeks ago
| Component: | Applications/WebPositive → Kits/Web Kit |
|---|---|
| Keywords: | wasm load removed |
| Summary: | WebPositive wasm worker goes berserk and eventually slows down the entire app to a halt → webkit: WASM high load |
| Version: | R1/beta5 → R1/Development |
How did you tie this to github, and not the obsidian site? also what do you mean slowd down the app? does it freeze?
comment:2 by , 5 weeks ago
It happens when opening some tabs (4-5 are usually enough) on sites that require the wasm engine, it seems, and GitHub is particular heavy on resources. CPU load his max and eventually WebPositive becomes completely unresponsive and locked up.
Note:
See TracTickets
for help on using tickets.
high CPU load in wasm thread