#Astro Failing to Build on Debian Systems (And not on Windows)

6 messages · Page 1 of 1 (latest)

magic escarp
#

Hello, long time viewer first time caller.

I host an Astro-based website (more or less using Astro as an over-engineered SSG) on GHP.
https://github.com/vipyrsec/vipyrsec-site

I've been running into issues getting the runner to build, specifically, I'm failing at "Optimizing Images" and producing a free(): invalid size error when it comes to generating optimized images.
An excerpt from our Github Actions log:

...
2024-02-20T17:51:46.3373510Z  generating optimized images 
2024-02-20T17:51:46.3500897Z free(): invalid size
2024-02-20T17:51:58.5593420Z Aborted (core dumped)
2024-02-20T17:51:58.5678556Z ##[error]Process completed with exit code 134.```

I noted that our original workflows seemed to be running Node 16, which I assumed was the issue here, so I went ahead and manually updated all our workflows, you can see that in Pull 51 here: 
https://github.com/vipyrsec/vipyrsec-site/pull/51

Moreover, I am able to successfully build the site in my local development environment in Windows, and it steps successfully through the image compression procedures. 

...
11:31:28 AM [build] 21 page(s) built in 4.58s
11:31:28 AM [build] Complete!```

To add to my... eternal puzzlement, I'm able to replicate this issue in a virtualized Debian-based system (Mint).

Completed in 144ms.
 generating optimized images 
  ▶ /_astro/logo_black.2da16de2_Z1n8n3Q.svg (before: 1kB, after: 1kB) (+6ms) (1/25)
free(): invalid size
Aborted (core dumped)

Anyone have any advice moving forward? Not entirely sure where this error is sourced from (or more specifically, why it's specifically affecting my Debian distros and not Windows.)

frigid pier
magic escarp
#

Ah my google-fu was not up to snuff it seems.

#

Let's see if that fixes it!

frigid pier
#

haha

#

gl