"SIGSEGV: segmentation violation" On Debian-based Distributions

[BoweFlex]

Describe the bug

When running freeze on Popos or an Ubuntu VM I receive an almost immediate segmentation fault. It is a different error (and much longer) when using freeze execute, but it seems to be the same essential problem. I've tried running both freeze and freeze execute on Fedora and have had no issues (files I'm using are the same).

To Reproduce
Steps to reproduce the behavior:

1. Run freeze <filename> or freeze execute "echo 'hello'" -o hello.png.
2. See error.

Expected behavior
Images of code should be saved without seg fault errors.

Screenshots

Desktop (please complete the following information):

• OS: Popos & Ubuntu
• Browser: Not sure it's relevant but Firefox
• Version: 22.04 LTS & 24.04 LTS

Additional context
Attempted resolution:
Tried both with go 1.22 and 1.24 on Ubuntu.
Tried building from source and installing the provided .deb.

[Kacaii]

Running ubuntu on WSL2, same thing here.

[luca-af]

Running Fedora 42, same error

[alantonica]

Same error on

Linux version 6.10.14-linuxkit

[pmessan]

Same on Ubuntu 24.04

[cognifloyd]

I'm getting similar errors on ubuntu 22.04.

Using the goland debugger, and the latest freeze sources on main, I traced the "runtime: split stack overflow" panic.

This line in the freeze sources is responsible for calling NewPixmap in resvg-go:
https://github.com/charmbracelet/freeze/blob/v0.2.2/png.go#L59

That ends up creating internal.TinySkiaPixmapNew:
https://github.com/kanrichan/resvg-go/blob/63db194ca9f56617cd99063eae9873dc5ada8f4a/pixmap.go#L19

Which uses wazero to run some rust via wasm here:
https://github.com/kanrichan/resvg-go/blob/63db194ca9f56617cd99063eae9873dc5ada8f4a/internal/resvg.go#L685-L690

The panic is triggered somewhere during the wasm run or the wasm exit code processing. I saw different wasm exit codes while tracing that were not always consistent. That includes: wazevoapi.ExitCodeGrowMemory and wazevoapi.ExitCodeIntegerOverflow.

I even tried updating to latest resvg-go commit that updates the version of wazero, but that did not make a difference. Oddly enough go resolved wazero 1.8.0 even though that commit specified 1.7.3, so that's probably why that didn't make a difference.

However, digging through the code, I came across support for rsvg-convert which bypasses the resvg lib that isn't working. I installed librsvg2-bin and that seems to work for me, avoiding the panic. I agree with this comment -- why doesn't the README mention installing it?
#51 (comment)