Memory leak of Crowd navigation

sevenPlus · February 23, 2023, 8:36am

Hi there,
when i use reacastJSPlugin of BABYLON, it costs a large memory footprint. And after applying to the mobile device, my phone can not open the page.
So I check the playground demo, and below is the memory footprint case. It is about 930KB.

Cedric · February 23, 2023, 8:44am

I’ve just tried with Edge, and I get a reasonable memory footprint compared to 2 other simple playgrounds

About 200Mb for the navmesh playground or the default one. Did you do something specific to get that number? Did you interact with the navigation playground?

EDIT: I’ve just tried on my Android phone without issue.

sevenPlus · February 23, 2023, 9:29am

I did not interact with the scene. And for this playground demo, the only thing is initiating the plugin.

It is about 860Mb and can not apply to mobile phones for long term using.
And could you test this demo. it is to navigate on a mesh inspired by PatrolJS for ThreeJS.

About 38Mb for navigation. Is there any way to fix this memory footprint using?

Cedric · February 23, 2023, 9:40am

If you open a tab with Babylon.js Playground (babylonjs.com) what is the footprint?
I’d be happy to fix that, I just need to know how it happens.

sevenPlus · February 23, 2023, 11:50am

This small scene is about 215Mb.

Cedric · February 23, 2023, 12:37pm

Any tool or howto to detect how this huge footprint happens @sebavan ?

sebavan · February 23, 2023, 6:53pm

sebavan · February 24, 2023, 12:34am

I looked a bit more and I can experience the same, the basic scene https://playground.babylonjs.com/#X5XCVT#649 is:

The one with recast initialized https://playground.babylonjs.com/#X5XCVT#645 is:

From the memory tools in chrome the snapshot shows that all of the overhead is the actual HEAP of the recast plugin. It probably means it is initialized like this:

sebavan · February 24, 2023, 12:34am

Cedric · February 24, 2023, 9:00am

I’ll check the build to see the amount of pre-allocated memory.

sevenPlus · February 27, 2023, 1:25am

Plz let me know if there is any progress. Thanks

sevenPlus · March 6, 2023, 2:43am

Should I open an issue on Github for this?

Cedric · March 6, 2023, 1:01pm

Yes please !

sebavan · March 7, 2023, 3:48pm

FYI @Cedric Memory leak of Crowd navigation · Issue #13595 · BabylonJS/Babylon.js · GitHub We could probably start with smaller footprint and dynamic memory or is it too slow ?

Cedric · March 7, 2023, 5:41pm

I’ve checked the build and the allocated size parameter is 64Mb

github.com

BabylonJS/Extensions/blob/330710ee4333834d29d1474773c466e2c3fc6e70/recastjs/CMakeLists.txt#L72


      
          )
          
          
SET(EXE_NAME "recast")
          
          
ADD_LIBRARY(${EXE_NAME} ${SRC_FILES} ${RECASTDETOUR_FILES})
          
          
# Build Release by default
          set(CMAKE_BUILD_TYPE Release CACHE STRING "Build Type")
          
          
# Default is 64*1024*1024 = 64MB
          set(TOTAL_MEMORY 67108864 CACHE STRING "Total Memory")
          
          
# Enable for resizable heap, with some amount of slowness
          set(ALLOW_MEMORY_GROWTH 0 CACHE STRING "Allow Memory Growth")
          
          
set(EMCC_ARGS
            -flto
            --post-js glue.js
            --post-js ${RECAST_ONLOAD_FILE}
            -O3
            -s ALLOW_MEMORY_GROWTH=${ALLOW_MEMORY_GROWTH}

so, I think it’s a bit more complex than changing the build options. 1st thing to do is to try to repro in a new project.

Cedric · March 8, 2023, 2:06pm

There is a fix ! update recast.js with lower memory usage by CedricGuillemet · Pull Request #13609 · BabylonJS/Babylon.js · GitHub

sevenPlus · March 8, 2023, 2:21pm

That’s so great! Thanks for your updating.