Open yarin-zhang opened 7 months ago
Related issues: https://github.com/yisibl/resvg-js/issues/287
Same error with some PNG images
PNG image below is not working
defineOgImageComponent('Default', {
url: 'https://upload.wikimedia.org/wikipedia/commons/thumb/6/6a/PNG_Test.png/477px-PNG_Test.png',
})
But PNG image below is working
defineOgImageComponent('Default', {
url: 'https://images.ctfassets.net/y1cdw1ablpvd/2G9eUljiJXW11zOTpqRSUk/0e41dc83190b8be5d6ea8ec58d83da90/blog_image.png',
})
the component is very simple just img text and a few static text
https://commons.wikimedia.org/wiki/File:PNG_Test.png contains pixels with alpha channel aka transparency.
https://github.com/yisibl/resvg-js/issues/287#issuecomment-1884768882
Also, I don't know if this is related, but even when it doesn't crash, resvg-js never carried over any opacity values to the PNG. I'm using fill-opacity (which is actually a better idea in my case anyway) but that's surely not quite right.
I used @nuxtjs/seo in my Nuxt 3.11.2 project and created ogImages for multiple pages according to the nuxt-og-image documentation.
OGImage can be displayed normally in both development and production environments.
My project was packaged and deployed through Docker.After one of my code updates, the Docker container started randomly reporting errors and crashing and exiting. The final log is as follows:
This error is a Rust error, which is not common in Node projects. Due to the mention of resvg, and the fact that only the nuxt og image project in the entire project relies on resvg, I think my issue should be raised here to see if this is a common error. If this is an upstream error, I think I should go to Resvg to raise an issue.
I am unable to provide a replica as this error occurred randomly three times in Docker, but did not occur in the development environment. And usually after running for a period of time (about a few hours), there is no direct correlation with the performance, disk space, etc. of the host.
My yarn.lock dependencies are as follows: