Segfault when .env is exactly 159 bytes

[jakeboone02]

What version of Bun is running?

0.6.5

What platform is your computer?

Linux 5.15.90.1-microsoft-standard-WSL2 x86_64 x86_64 (also same behavior on macOS)

What steps can reproduce the bug?

# Create empty dir and cd into it
mkdir testenv159
cd testenv159
# Create `.env` file of exactly 159 bytes
echo "123456789=1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678" > .env
# Check length is 159
ls -l .env
# Create dummy JS file to run
echo 'console.log("Hello, 159-byte .env!")' > test.js
# Segfault here:
bun test.js

What is the expected behavior?

Bun should not segfault.

What do you see instead?

bun test.js
[0.02ms] ".env"
[1]    23032 segmentation fault  bun test.js

Additional information

I tried other lengths for .env like 318 (checking for multiples of 159), and adjacent lengths 158 and 160, etc. No matter what content was in the .env file, a length of 159 caused a segfault and any other length did not.

[trnxdev]

I can confirm this issue also exists on my machine (Arch Linux, 6.3.6-zen1-1-zen)
and some virtual machines on debian, windows (wsl using ubuntu)

[trnxdev]

This can be already be marked as closed @jakeboone02 seems like it was fixed in #3369

[alexlamsl]

Indeed − thank you @Jarred-Sumner 😉

[jakeboone02]

Wow I was hovering over the "Close issue" button about to click it when you closed it, @alexlamsl