On Mon, 25 May 2026 18:18:36 +0200, Otto Cooper <[email protected]> wrote: > > Back to the hugo package... > > >hugo version > hugo v0.160.1+extended+withdeploy openbsd/amd64 BuildDate=unknown > > While we are using the extended hugo binary, OpenBSD manages system memory > allocations (malloc) and system calls much more strictly than Linux or macOS > (e.g., using W^X write-xor-execute protections). > > Because modern Hugo uses a compiled WebAssembly (WASM) virtual machine layer > (libwebp translated via Go's internal warpc target) to process WebP images, > the Hugo binary is attempting to dynamically allocate executable memory pages > inside OpenBSD to compute the image resizing calculations. OpenBSD's kernel > prevents this by default for security, instantly killing the internal thread > and passing a generic failed to resize image error back to Hugo. > > Does this make sense now? > >
Some. Can you share an example of site which actually fails? -- wbr, Kirill
