Session: Error while trying to free lock for ci_session

2 is a bad decision in the first place.

It's necessary for performance as outlined in your documentation. None of the methods we call concurrently write session data. The library is auto-loaded for an auth check as our entire app is behind a login.

5 cannot happen because request B session_start() will block until request A's session_write_close() is complete. This is THE sole purpose of locking.

I have no idea what's going on then. Something isn't working properly if that scenario is supposed to be handled.