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
FontManager.RenderBitmap() access violation exception #1692
Comments
With the latest master commits, this also seems to happen randomly when modifying UI pages. More time needed to search how and why this is happening is required. Current stacktrace (2nd, I lost the first)
3rd consecutive stack trace
Next shown errors are the same as the 3rd. |
can you try in the fontmanager using this as line 144 and try to replicate it? using this stops stride from crashing when adding a UI page to a camera ( no idea if the font crashs then.. but stride doesnt anymore ) |
No effect. Your suggestion doesn't even make sense, atleast in my case, since |
Adding info here as I just faced the same issue. It seems to be specifically with BuildBitmapThread() in the FontManager.cs class if I remove the call to RenderBitmap(character, fontFace); the crashing stopped but the runtime rasterized fonts no longer worked. It also stopped crashing all together so I can no longer reproduce for some reason.. |
It's most likely a non deterministic bug. At least I don't understand the circumstances needed to exactly reproduce this issue. Behaviour may be different from each commit. YMMV. |
Fixed by #1999 . |
Release Type: Github
Version: Master git branch
Platform(s): Windows
Describe the bug
Creating and loading a new project results in Stride crashing at startup.
To Reproduce
Steps to reproduce the behavior:
inside
FontManager.cs
Expected behavior
I expected the scene to load sucessfully...
Log and callstacks
Callstack
Additional context
In the debugger,
FontFace.GlyphCount
throws a overflow error. Same withfontFace.StyleFlags
Update 1: I have found out that this issue doesn't exist on the lastest release 4.1.0.1838
The text was updated successfully, but these errors were encountered: