Yogurt's AI notes engine stability on Linux, specifically CPU model loading with large allocations and interaction with Electron's PartitionAlloc.
Raw Developer Origin & Technical Request
GitHub Issue
Nov 13, 2026
Yogurt 0.3.11 AppImage (Electron 44.7.2, node-llama-cpp 3.22.1), Linux x86_64, Ryzen 7 5700X (AVX2), 32 GB RAM, RTX 3060 Ti.
**Symptom.** Writing notes fails with `notes engine stopped (code 132)` on every attempt, with both gemma-4-E4B_q4_0 and gemma-4-26B_q4_0. The kernel logs `trap invalid opcode ... in yogurt-bin`.
**Cause.** The Electron binary exports Chromium's allocator shim (`malloc`, `posix_memalign`, ...), so libggml/libllama allocate through PartitionAlloc, which crashes on purpose on a single allocation above ~2 GiB. When the model runs on the CPU, llama.cpp repacks the q4_0 weights for AVX2 into one `CPU_REPACK` buffer: 2116 MiB for E4B and 13134 MiB for 26B. Under gdb the last call before the crash is `posix_memalign(64, 2219212800)`. The same binaries in plain Node 22 load and generate fine, because glibc mmaps large blocks.
**Why it ends up on the CPU.** In my case the startup probe logged `graphics: vulkan, 0.0 GB` (no device), so the "graphics card allowed" load put 0 layers on the GPU and crashed. After that `cpuOnly` stays set for the rest of the session, so every retry is CPU-only and crashes again. When the probe does see the card, both models load with GPU layers and work, because no CPU_REPACK buffer is created.
**Repro without the UI.** With Electron 44.7.2: `utilityProcess.fork(/out/main/engine.js, [], { env: { ...process.env, YOGURT_ENGINE_GPU: 'off' } })`, post `{type:'probe',id:1}`, then `{type:'load',id:2,modelPath:
Developer Debate & Comments
No active discussions extracted for this entry yet.
Adjacent Repository Pain Points
Other highly discussed features and pain points extracted from FrigadeHQ/yogurt.
Frequently Asked Questions
Market intelligence mapped to Yogurt's AI notes engine stability on Linux, specifically CPU model loading with large allocations and interaction with Electron's PartitionAlloc..
What is the technical positioning of Yogurt's AI notes engine stability on Linux, specifically CPU model loading with large allocations and interaction with Electron's PartitionAlloc.?
What is the general sentiment around Yogurt's AI notes engine stability on Linux, specifically CPU model loading with large allocations and interaction with Electron's PartitionAlloc.?
What architecture is tied to Yogurt's AI notes engine stability on Linux, specifically CPU model loading with large allocations and interaction with Electron's PartitionAlloc.?
Engagement Signals
Cross-Market Term Frequency
Counts stored text matches for foundational terms like AVX2 and Electron binary in analysed public discussions. These counts do not measure adoption.
Stored text matches, not adoption or market-share measurements.
- AVX2: 3 records
- Electron binary: 2 records
- notes engine dies: 1 records
- SIGILL (code 132): 1 records
- CPU_REPACK allocation: 1 records
- PartitionAlloc: 1 records
- allocator shim: 1 records
- libggml/libllama: 1 records
- posix_memalign: 1 records
- glibc mmaps: 1 records
- startup probe: 1 records
- graphics: vulkan, 0.0 GB: 1 records
- cpuOnly: 1 records
- utilityProcess.fork: 1 records
- gemma-4-E4B_q4_0: 1 records
- gemma-4-26B_q4_0: 1 records
SaaS Metrics