Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible memory leak in session controller #684

Open
SebCav opened this issue Dec 7, 2018 · 0 comments
Open

Possible memory leak in session controller #684

SebCav opened this issue Dec 7, 2018 · 0 comments

Comments

@SebCav
Copy link

SebCav commented Dec 7, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant