Security context in session grows with each load
Since the latest changes to security it seems something goes wrong with object serialization to the session. It grows exponentially with each page load until the memory limit is hit.
Reproducible by logging in and calling the same page again and again... Even failing login tries have that effect.
Updated by Karsten Dambekalns almost 12 years ago
- File sess_j6je3itierlcpkhic6hkgle600.first.txt sess_j6je3itierlcpkhic6hkgle600.first.txt added
- File sess_j6je3itierlcpkhic6hkgle600.second.txt sess_j6je3itierlcpkhic6hkgle600.second.txt added
Attached two session files. The file doubles it's size on every page load.
Updated by Karsten Dambekalns over 11 years ago
- Assignee changed from Robert Lemke to Karsten Dambekalns
- % Done changed from 50 to 90
The problem is caused by
seperateActiveAndInactiveTokens() in combination with the way
1. call initialize tokens 0 activeTokens 1 inactiveTokens 0 shutdownObject tokens 1 activeTokens 1 inactiveTokens 0 2. call initialize tokens 1 activeTokens 1 inactiveTokens 0 seperateActiveAndInactiveTokens tokens 1 activeTokens 2 (!) inactiveTokens 0 shutdownObject tokens 2 activeTokens 2 inactiveTokens 0 3. call initialize tokens 2 activeTokens 2 inactiveTokens 0 seperateActiveAndInactiveTokens tokens 2 activeTokens 4 (!) inactiveTokens 0 shutdownObject tokens 4 activeTokens 4 inactiveTokens 0
Updated by Bastian Waidelich about 11 years ago
- Status changed from Accepted to Resolved
- Assignee changed from Bastian Waidelich to Karsten Dambekalns
Bastian Waidelich wrote:
It seems this issue reoccurs in the current version.. I'll dig into it
Apparently the issue occurred because I had configured multiple authentication providers - so it might be just a misconfiguration. I'll check that and reopen the issue in case it is not.