Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Got a lot of errors.

ERROR: 1 RID allocations of type 'N5GLES312RenderTargetE' were leaked at exit.

ERROR: 23 RID allocations of type 'N5GLES37TextureE' were leaked at exit.

ERROR: Texture with GL ID of 18: leaked 1364 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 26: leaked 1364 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 34: leaked 348 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 39: leaked 760 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 43: leaked 684 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 44: leaked 684 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 45: leaked 1364 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 47: leaked 1364 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 56: leaked 1364 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 57: leaked 1364 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 58: leaked 1364 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 65: leaked 2732 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 66: leaked 2732 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 67: leaked 2732 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 68: leaked 2732 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 69: leaked 2732 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 70: leaked 2732 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 71: leaked 2732 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 72: leaked 2732 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 73: leaked 1364 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: Texture with GL ID of 103: leaked 131072 bytes.

   at: ~Utilities (drivers/gles3/storage/utilities.cpp:77)

ERROR: 17 RID allocations of type 'N18RendererCanvasCull4ItemE' were leaked at exit.

ERROR: 1 RID allocations of type 'N18RendererCanvasCull6CanvasE' were leaked at exit.

ERROR: 1 RID allocations of type 'N16RendererViewport8ViewportE' were leaked at exit.

ERROR: 8 RID allocations of type 'PN18TextServerAdvanced22ShapedTextDataAdvancedE' were leaked at exit.

ERROR: 1 RID allocations of type 'PN18TextServerAdvanced12FontAdvancedE' were leaked at exit.

WARNING: ObjectDB instances leaked at exit (run with --verbose for details).

     at: cleanup (core/object/object.cpp:2047)

These are after you close the game, that's why I mentioned that the logs should be checked before closing. All of these are unrelated and are just assets not being fulled unloaded on game close, it shouldn't affect anything. Is this the entire log that was output to the console?

PS C:\EsriPress\Feraline> ./Feraline.exe

PS C:\EsriPress\Feraline> Godot Engine v4.1.2.rc1.official.58f0cae4a - https://godotengine.org

OpenGL API 3.3.0 - Build 25.20.100.6617 - Compatibility - Using Device: Intel - Intel(R) UHD Graphics 620

just this

Did that help at all?

Unfortunately not.. there are no errors there. Have you downloaded the latest build? Another person with the same issue no longer has the issue after updating.

(+1)

Huh, that worked, must have been something with the version. Coding sure can be finicky. 

(+1)

Thanks for the help by the way excited to try it out.

No problem, I'm glad it's working for you now ^^