You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Raylib has memory leak in Shader unloading. When it could not load shader library put default shaders descriptors to creating structure. But when I unload this shader locs array is not freed.
@nagolove Good catch! Thanks for reporting! Just added a quick fix to make sure the default shader locations are returned in case of default shader fallback... but default shader fallback was supposed to be removed in latest raylib 5.5 release! Other fallback mechanisms have already been removed in the last few years (models, fonts, textures).
I'm keeping this issue open while I review the full shader system because avoiding fallback could generate some crash.
raysan5
changed the title
[rcore] memory leak in UnloadShader()
[rcore] UnloadShader(), new shader locations are not properly freed when shader fallback to default
Dec 28, 2024
Issue description
Raylib has memory leak in
Shader
unloading. When it could not load shader library put default shaders descriptors to creating structure. But when I unload this shaderlocs
array is not freed.raylib/src/rcore.c
Lines 1411 to 1420 in 7ecc47d
Environment
OS: Arch Linux x86_64
Raylib version: b079679
Code Example
Build command
The text was updated successfully, but these errors were encountered: