please fix.
According to the docs, is deprecated and has been replaced by .
This should definitely be fixed, since apparently can lead to memory leaks when still used.
I totally agree with @cybrox, except sometimes you can even get away by doing , rather than .
It's all up to you, though.
Don't forget to call or you might end up with memory corruption, be careful. And remember, mutates, so don't forget to clone .
Look thoroughly, this leak has negative sign, so each nocode run gives you additional memory. Effect is persistent. When your memory achieves 64GB, memory will be added to your neighborhoods.
It seems your memory is too low. Be aware that the project contains nothing.
I suggest clear cache, then restart your device. Working for me...
Cannot reproduce this problem, please buy a new MacBook
Dzenly//no code = peace and love, let's kill codes
@hanseul1795
The peace contains the idea of hatred, the 'no code' contains the idea of code.
I will just watch and meditate.
@Dzenly Wise word from the master, I'll meditate it also. ZEN!
Most helpful comment
According to the docs,
is deprecated and has been replaced by.This should definitely be fixed, since apparently
can lead to memory leaks when still used.