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
PHP has its own memory management APIs, i.e., ecalloc, efree, etc, so that allocated memories will be freed up in the end of request if it wants.
However, when a connection is not closed, while all memories allocated by PDO layers will be freed automatically, the memories in Snowflake Client layer won't be, because those memories are allocated SF_CALLOC and SF_FREE that currently simple mapping to the system functions calloc and free. This will yield memory leak.
Snowflake Client/Connector should have a mode that does similar to PHP memory manager such that the memories are automatically freed in each of snowflake_*term function calls.
The text was updated successfully, but these errors were encountered:
Alternatively would be it be good idea that the application can provide CALLOC, MALLOC, FREE call backs? This way, the application can specify the memory manager if desired.
PHP has its own memory management APIs, i.e., ecalloc, efree, etc, so that allocated memories will be freed up in the end of request if it wants.
However, when a connection is not closed, while all memories allocated by PDO layers will be freed automatically, the memories in Snowflake Client layer won't be, because those memories are allocated SF_CALLOC and SF_FREE that currently simple mapping to the system functions calloc and free. This will yield memory leak.
Snowflake Client/Connector should have a mode that does similar to PHP memory manager such that the memories are automatically freed in each of snowflake_*term function calls.
The text was updated successfully, but these errors were encountered: