-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error "fatal runtime error: failed to initiate panic, error 5" in Docker #199
Comments
Related issues: thx/resvg-js#287 |
Same error with some PNG images PNG image below is not working
But PNG image below is working
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.
|
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:
The text was updated successfully, but these errors were encountered: