-
Notifications
You must be signed in to change notification settings - Fork 24
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 with sessions #25
Comments
This is not easy to solve. Exposing the variable globally: bad. Exposing the variable to cgi.c only: not possible without exposing it globally (?). This whole concept of global variables in a library is broken, but for v1.x we can't change it anymore, if we want to maintain API compatibility. I propose adding a new function like |
Moved this to milestone v1.2, because introducing a new function would extend the API which would trigger a minor version bump with semantic versioning. |
This fixes a possible memory leak when working with sessions (especially with some non-mainline fcgi patches). Quoting from the ticket: The global variable `sess_fname` is a pointer to dynamically allocated memory which happens either in `sess_generate_id()` or in `cgi_session_start()`. However this memory is never freed. To not expose the variable globally or even just to `cgi.c` where e.g. `cgi_end()` could access it, a new API function is introduced. We leave bumping the API version up to a follow up commit. fixes rafaelsteil#25 Signed-off-by: Alexander Dahl <[email protected]>
This is a follow-up to rafaelsteil#25 to ensure this all works like it should without evil memory leaks, null pointer dereferences, … Now the first test here is very simple, just to get this test module running. Signed-off-by: Alexander Dahl <[email protected]>
This fixes a possible memory leak when working with sessions (especially with some non-mainline fcgi patches). Quoting from the ticket: The global variable `sess_fname` is a pointer to dynamically allocated memory which happens either in `sess_generate_id()` or in `cgi_session_start()`. However this memory is never freed. To not expose the variable globally or even just to `cgi.c` where e.g. `cgi_end()` could access it, a new API function is introduced. We leave bumping the API version up to a follow up commit. fixes rafaelsteil#25 Signed-off-by: Alexander Dahl <[email protected]>
This is a follow-up to rafaelsteil#25 to ensure this all works like it should without evil memory leaks, null pointer dereferences, … Now the first test here is very simple, just to get this test module running. Signed-off-by: Alexander Dahl <[email protected]>
This is a follow-up to rafaelsteil#25 to ensure this all works like it should without evil memory leaks, null pointer dereferences, … Now the first test here is very simple, just to get this test module running. Signed-off-by: Alexander Dahl <[email protected]>
This fixes a possible memory leak when working with sessions (especially with some non-mainline fcgi patches). Quoting from the ticket: The global variable `sess_fname` is a pointer to dynamically allocated memory which happens either in `sess_generate_id()` or in `cgi_session_start()`. However this memory is never freed. To not expose the variable globally or even just to `cgi.c` where e.g. `cgi_end()` could access it, a new API function is introduced. We leave bumping the API version up to a follow up commit. fixes rafaelsteil#25 Signed-off-by: Alexander Dahl <[email protected]>
This is a follow-up to rafaelsteil#25 to ensure this all works like it should without evil memory leaks, null pointer dereferences, … Now the first test here is very simple, just to get this test module running. Signed-off-by: Alexander Dahl <[email protected]>
This fixes a possible memory leak when working with sessions (especially with some non-mainline fcgi patches). Quoting from the ticket: The global variable `sess_fname` is a pointer to dynamically allocated memory which happens either in `sess_generate_id()` or in `cgi_session_start()`. However this memory is never freed. To not expose the variable globally or even just to `cgi.c` where e.g. `cgi_end()` could access it, a new API function is introduced. We leave bumping the API version up to a follow up commit. fixes rafaelsteil#25 Signed-off-by: Alexander Dahl <[email protected]>
This is a follow-up to rafaelsteil#25 to ensure this all works like it should without evil memory leaks, null pointer dereferences, … Now the first test here is very simple, just to get this test module running. Signed-off-by: Alexander Dahl <[email protected]>
This fixes a possible memory leak when working with sessions (especially with some non-mainline fcgi patches). Quoting from the ticket: The global variable `sess_fname` is a pointer to dynamically allocated memory which happens either in `sess_generate_id()` or in `cgi_session_start()`. However this memory is never freed. To not expose the variable globally or even just to `cgi.c` where e.g. `cgi_end()` could access it, a new API function is introduced. We leave bumping the API version up to a follow up commit. fixes rafaelsteil#25 Signed-off-by: Alexander Dahl <[email protected]>
This is a follow-up to rafaelsteil#25 to ensure this all works like it should without evil memory leaks, null pointer dereferences, … Now the first test here is very simple, just to get this test module running. Signed-off-by: Alexander Dahl <[email protected]>
This fixes a possible memory leak when working with sessions (especially with some non-mainline fcgi patches). Quoting from the ticket: The global variable `sess_fname` is a pointer to dynamically allocated memory which happens either in `sess_generate_id()` or in `cgi_session_start()`. However this memory is never freed. To not expose the variable globally or even just to `cgi.c` where e.g. `cgi_end()` could access it, a new API function is introduced. We leave bumping the API version up to a follow up commit. fixes rafaelsteil#25 Signed-off-by: Alexander Dahl <[email protected]>
This is a follow-up to rafaelsteil#25 to ensure this all works like it should without evil memory leaks, null pointer dereferences, … Now the first test here is very simple, just to get this test module running. Signed-off-by: Alexander Dahl <[email protected]>
This fixes a possible memory leak when working with sessions (especially with some non-mainline fcgi patches). Quoting from the ticket: The global variable `sess_fname` is a pointer to dynamically allocated memory which happens either in `sess_generate_id()` or in `cgi_session_start()`. However this memory is never freed. To not expose the variable globally or even just to `cgi.c` where e.g. `cgi_end()` could access it, a new API function is introduced. We leave bumping the API version up to a follow up commit. Fixes: rafaelsteil#25 Signed-off-by: Alexander Dahl <[email protected]>
This is a follow-up to rafaelsteil#25 to ensure this all works like it should without evil memory leaks, null pointer dereferences, … Now the first test here is very simple, just to get this test module running. Signed-off-by: Alexander Dahl <[email protected]>
The global variable
sess_fname
is a pointer to dynamically allocated memory which happens either insess_generate_id()
or incgi_session_start()
. However this memory is never freed.The text was updated successfully, but these errors were encountered: