Deploying 11ty v3.0.0 to pages keeps failing

For Workes & Pages, what is the name of the domain?

No domain yet

What is the error number?

139

What is the error message?

20:24:09.305 Segmentation fault 20:24:09.316 Failed: Error while executing user command. Exited with error code: 139 20:24:09.328 Failed: build command exited with code: 1 20:24:10.277 Failed: error occurred while running build command

What is the issue or error you’re encountering

Segmentation fault - Failed: Error while executing user command. Exited with error code: 139

What steps have you taken to resolve the issue?

None as yet, it’s a brand-new build using 11ty v3.0.0. I’m not sure how I can change anything. This is the first time I’ve used Pages. I plan on migrating from Netlify to CFP

What are the steps to reproduce the issue?

Point CFP at my GitHub 11ty repository and let it attempt to build.

11ty 3.0.0 now does numerous image transformations during the build phase, so I wonder if this is a memory issue? This article mentions the fact that code 139 is a memory issue. Any ideas? Are there memory settings in CFP I can use to test this theory?

Screenshot of the error

Just to update folks, I’ve managed to get it to build by restricting the eleventyImageTransformPlugin to only output WebP images (I removed AVIF).

The transform plugin uses the sharp image processor, and transforming to Avif is very resource intensive, so I think this could be an issue that pops up a lot over the coming months as people migrate to 11ty v3.0.0 & "@11ty/eleventy-img": "^5.0.0".

I’m not sure if this is something CF can anticipate and maybe adjust the build agents to allow for these transforms in the future?

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.