Operating system
Windows
Joplin version
3.6.15
Desktop version info
Joplin 3.6.15 (Windows x64)
Windows 10 22H2 (19045.7548)
20 GB RAM (~40% free during import)
Joplin 3.6.15 (prod, win32)
Device: win32, Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz
ID клієнта: ce94d3aeb6b84262b5e0400aca069d81
Версія синхронізації: 3
Версія профайлу: 49
Підтримка Keychain: Так
Alternative instance ID: -
Sync target: OneDrive
Редактор: Розширений текст
Ревізія: c615726
Backup: 1.5.1
Freehand Drawing: 4.3.0
Current behaviour
Steps
Import a normal .one notebook (~150 MB).
Import starts.
Joplin reports:
RangeError: WebAssembly.Instance(): Out of memory:
Cannot allocate Wasm memory for new instance
Stack points to:
@joplin/onenote-converter/renderer/pkg/renderer.js
After that Joplin reports:
Failed to load @joplin/onenote-converter
This is misleading because the package is present and the actual failure is the WebAssembly initialization.
Additional observation
On two occasions Windows later crashed with BSOD (0x139 INVALID_BALANCED_TREE, ImgLock.sys), but I'm not claiming Joplin caused it. The reproducible problem is the WebAssembly initialization failure.
Expected behaviour
No response
Logs
No response
Operating system
Windows
Joplin version
3.6.15
Desktop version info
Joplin 3.6.15 (Windows x64)
Windows 10 22H2 (19045.7548)
20 GB RAM (~40% free during import)
Joplin 3.6.15 (prod, win32)
Device: win32, Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz
ID клієнта: ce94d3aeb6b84262b5e0400aca069d81
Версія синхронізації: 3
Версія профайлу: 49
Підтримка Keychain: Так
Alternative instance ID: -
Sync target: OneDrive
Редактор: Розширений текст
Ревізія: c615726
Backup: 1.5.1
Freehand Drawing: 4.3.0
Current behaviour
Steps
Import a normal .one notebook (~150 MB).
Import starts.
Joplin reports:
RangeError: WebAssembly.Instance(): Out of memory:
Cannot allocate Wasm memory for new instance
Stack points to:
@joplin/onenote-converter/renderer/pkg/renderer.js
After that Joplin reports:
Failed to load @joplin/onenote-converter
This is misleading because the package is present and the actual failure is the WebAssembly initialization.
Additional observation
On two occasions Windows later crashed with BSOD (0x139 INVALID_BALANCED_TREE, ImgLock.sys), but I'm not claiming Joplin caused it. The reproducible problem is the WebAssembly initialization failure.
Expected behaviour
No response
Logs
No response