Replies: 1 comment
-
|
I had this issue and found I had to compile with BGFX_CONFIG_MULTITHREADED=0 for the bgfx project. Apparently mulithread doesn't like this cycle and the renderFrame before init still doesn't shut off multithreading code. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I know I've already asked quite a bit of questions in here already, so let me take the time to thank you all for an outstanding library and a great community.
I've ported over some of my OpenGL functionality into BGFX and am noticing a crash in BGFX when we execute our unit tests. Our unit tests run in a way that setup and tear down our system multiple times to test proper initialization and shutdown. This was setup using an OpenGL context within a GLFW window.
With the transition to BGFX I've noticed that the first test will run with no issue, but the second test crashes. I tried to isolate the test that caused the crash and running the test by itself passes. I created a basic sample program that initializes a GLFW window and inits BGFX before shutting down and repeating the process (Which can be found below). I noticed the crash was caused from an existing issue and tried to try again with multi-threading disabled and get a different crash of
BGFX_FATAL(NULL != m_hdc, Fatal::UnableToInitialize, "GetDC failed!");Any advice would be greatly appreciated
Beta Was this translation helpful? Give feedback.
All reactions