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
Hi,
my company is using an old version of Chicago Boss, but from a quick look at the current code it seems the issue we found is still relevant.
We have a boss application which uses sessions provided by boss_session_adapter_mock, and there is a scenario where there is only one single client active, making ~20 connections per second with no session-cookie defined.
This results in boss_sesson_controller:handle_call({new_session, undefined}, _, State) being called 20 times per second, which in turn calls boss_session_adapter_mock:session_exists(_,undefined). The lines 39-40 of boss_session_adapter_mock.erl are preventing the cleanup-code in boss_session_mock_controller:handle_call({session_exists...) to be called, resulting in a huge memory leak after a few hours even if session_exp_time is set to a very low value.
In any case, I am not sure if our code is making a bad use of sessions and this triggers the problem, or if this is really a bug.
The text was updated successfully, but these errors were encountered:
Hi,
my company is using an old version of Chicago Boss, but from a quick look at the current code it seems the issue we found is still relevant.
We have a boss application which uses sessions provided by boss_session_adapter_mock, and there is a scenario where there is only one single client active, making ~20 connections per second with no session-cookie defined.
This results in boss_sesson_controller:handle_call({new_session, undefined}, _, State) being called 20 times per second, which in turn calls boss_session_adapter_mock:session_exists(_,undefined). The lines 39-40 of boss_session_adapter_mock.erl are preventing the cleanup-code in boss_session_mock_controller:handle_call({session_exists...) to be called, resulting in a huge memory leak after a few hours even if session_exp_time is set to a very low value.
In any case, I am not sure if our code is making a bad use of sessions and this triggers the problem, or if this is really a bug.
The text was updated successfully, but these errors were encountered: