Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Runtime Error

See original GitHub issue

some images do not load. does anyone know how i can solve this ?

npx @squoosh/cli --jxl '{"speed":1,"quality":100,"progressive":true,"epf":-1,"nearLossless":0,"lossyPalette":true}' 45.png
npx: installed 2 in 2.31s
0/1 / ▐▨▨▨▨▨╌╌╌╌╌▌ Encoding (6 threads)
 45.png: 35.92MBundefined
Worker error:  Error [RuntimeError]: abort(RuntimeError: abort(undefined). Build with -s ASSERTIONS=1 for more info.). Build with -s ASSERTIONS=1 for more info.
    at process.w (C:\Users\Ti\AppData\Roaming\npm-cache\_npx\23976\node_modules\@squoosh\cli\build\index.js:7:376640)
    at process.emit (events.js:327:22)
    at processPromiseRejections (internal/process/promises.js:209:33)
0/1 - ▐▨▨▨▨▨╌╌╌╌╌▌ Encoding (6 threads)
 45.png: 35.92MB

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:6

Top GitHub Comments

1reaction

surmacommented, Dec 22, 2020

So yeah, OxiPNG being slow on a 7159 x 4742‬ image is expected. If you use the PWA, it will use threads for OxiPNG. The CLI doesn’t do that yet. But PNG is a horrible format for big images anyway.

Overall the issue here is actually not the size of the image in general, but only in the context of JPEG-XL. And that codec is still unstable. I am going to close this as there is not much to do on our end except wait that the JPEG-XL encoder stabilizes.

1reaction

surmacommented, Dec 22, 2020

Ah it’s a big image. Yeah, that is most likely the cause. Technically, there is nothing keeping us from handing ~150MB of RGBA data, but I know that big images currently cause issues.