-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Assertion failed: (!scaled_font->cache_frozen), function _cairo_scaled_glyph_page_destroy, file cairo-scaled-font.c, line 459. Abort trap: 6 #912
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
Comments
I have since tried a few things that looked like possible solutions around the web. I tried opening FontBook on my Mac and validating all of the fonts and double checked that the fonts I am trying to use to fillText exist on my system. They do and are all now validated. No change in error message. Seems to be a not uncommon issue related to using Cairo. Here are posts in other places about this same issue, but using different technologies on top of Cairo: When using ImageMagick: http://www.imagemagick.org/discourse-server/viewtopic.php?t=31736 I'm leaning toward this issue being caused by a bad font file or something in Cairo not installed correctly on my machine making Cairo unable to understand the font I am asking it to use to |
Started digging through old closed issues on the repo and found in #837 that uninstalling Pango and doing a rebuild fixed someone else's issues with rendering text. Ran Now I am no longer getting the error: |
Uninstalling Pango and rebuilding would give you the non-pango build instead of the pango build, which are very different from each other (see #715). Ideally you want the Pango build since it'll give you more features (more glyphs, languages, etc). I have never seen an error like that though so I don't know if I can help. If you really want to narrow down the issue you could start with a minimal Pango+Cairo program in C. |
Any updates on this? |
I think this was an issue in the Cairo font system, which we don't use anymore (try it with |
No, still the same error with [email protected]. |
After reinstalling the brew packages and with [email protected] the error is gone |
I am still experiencing this problem. |
I still have this with [email protected] |
I was using [email protected] and it was working fine... but after I upgraded to [email protected] I'm getting this issue |
@ophinjay were you using a prebuilt .12 and a from-source-build of .13? What platform? |
@zbjornson No it was prebuilt version of .13 not compiled from source... did npm install canvas2.0.0-alpha.13.. that is the prebuit version right... I'm on MacOS.. I also tried uninstalling all the dependencies |
@ophinjay there's no prebuilt version of .13 yet (releases listed here), so my question should have just been "are you using prebuilt .12 or building from source?" I'm not sure about the MacOS situation, but prebuilt .12 may have come with a newer version of pango than the one you have locally that was used when building .13 from source. |
Get always the same issue - Assertion failed: (!scaled_font->cache_frozen), function _cairo_scaled_glyph_page_destroy, file cairo-scaled-font.c, line 459. I try to load manually the font and this:https://medium.com/@adamhooper/fonts-in-node-canvas-bbf0b6b0cabf, but get the issue too. When i uninstall pango, nothing works. |
When I use canvas-prebuilt it works for me. Find the solution here: #837 |
Issue
I seem to be hitting a bug when using ctx.fillText. In the code sample below, I can do ctx.fillRect fine and do get a rectangle output with the correct color and dimensions, but the text string errs. If I comment out the
ctx.fillText("Hello World", 100, 100);
line, the canvas builds the image as expected. Obviously, I'd like to stick some text on top of the canvas before the image file is generated, but .fillText gives the following error:Assertion failed: (!scaled_font->cache_frozen), function _cairo_scaled_glyph_page_destroy, file cairo-scaled-font.c, line 459. Abort trap: 6
Steps to Reproduce
Your Environment
The text was updated successfully, but these errors were encountered: