Kai O'Reilly
Kai O'Reilly
I can confirm that this still happens: the demo starts at 142 MB of memory usage on web, and then climbs to at least 506 MB. It seems to only...
This definitely only happens when the tab / window is not open / focused.
I appear to have fixed the most severe memory leak issue in 3dcf77a, which resulted in apps crashing on mobile web due to excessive memory usage. It seems like there...
Just to be clear, the scrolling issue is that memory usage reliably and significantly increases when you scroll, and this increase persists as you continue to scroll. A good example...
Actually, the excessive memory usage crash still seems to be happening on desktop occasionally.
The crash on Android web is still happening, and I determined after hours of debugging that this issue is actually not a memory leak, but a bizarre wasm compilation /...
As of a2313f0, we are now (at least temporarily) using a different markdown library, which prevents this issue from happening.
This has been largely implemented (see https://github.com/goki/goki), but more work needs to be done, so I will keep this issue around as a reminder for the v2 milestone.
Also, in `goki init`, we need to automatically get the org from the mod url / filepath, automatically get the version package, and initialize the icons if it is an...
The config structure of the goki tool also needs to be improved, as we should probably get rid of the output and package fields and stop supporting multiple targets, as...