4.29 Memory Leak on StreamLayer

[orahlagi]

Hello, Our product is using StreamLayer with a vast amount of updates, that are sent through "sendMessageToClient" API.

After ±20 minutes of use, the map becomes blank, and a large amount of errors such as :

TypeError: Cannot read properties of undefined (reading 'memoryStats')

at get memoryStats


And: Array buffer allocation failed

are popping up. so the map gets stuck and hundreds of errors are stacked.

We verified that it only happens on 4.29, downgrade to 4.28 resolves this.

Pretty tough for me to reproduce this on a sandbox because of the nature of the data and update amount.

If this can be fixed before 4.30 it would be very helpful.

Thanks.

[UndralBatsukh]

We will take a look into this behavior. Can you please give me some specifics on how many features, what kind of updates  and update frequency? thanks

[orahlagi]

Approx 5000 features spread on 3 Stream layers

around 1000 updates a min that include movements of the features (by updating the location)

Running 4.29 on any other environment that includes a bit fewer features / movements works fine and doesn't crash. only on intensive env. 4.28 on the same env is perfectly fine.