-
Hello everyone, I just noticed that after bgfx shutdown, this message gets logged: MEMORY LEAK: Number of leaked blocks 437 (Max blocks: 581) with number of blocks varying between runs. Does anyone have an idea where to start hunting these leaks? all the memory passed on to bgfx is allocated outside and referenced using bgfx::makeref(tiny static vertex buffers/index and huge *uint_8ts for texture data). The amount of data is the same between runs. thanks for any pointers;) nesa |
Beta Was this translation helpful? Give feedback.
Answered by
bkaradzic
Jul 26, 2022
Replies: 1 comment 1 reply
-
Look for any |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
npnp
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Look for any
bgfx::makeRef
orbgfx::alloc*
that's not passed to bgfx API. All those must be passed to bgfx API, otherwise you'll have leak.