michael-e

Ooops, sorry, I messed it all up.

No, no events. I am just editing an entry in the Symphony backend (Content > …). I also have no idea why this commit is the issue.

Yep, I did it like this: - delete all rows from the sessions table - log in to Symphony -> one session is created, as you mentioned above - edit...

So for some reason new XSRF tokens are generated, which are saved to new sessions.

I just double-checked, again: - Check out e530d0b8630483189ff56c03c1e6561a1e95dc1a (or later): broken behaviour. - Check out one commit earlier (6d239fc7dd234d959b3c61017e264df074179458): everything OK.

I even tried current integration. :-( Ah, wait, I disabled some extensions now, and now it works fine. So I will try and find out which extension does it!

OK, here we go: Do you remember the problems I had with a special (private) extension when the autoloader was introduced? Because the extension is running background processes, I had...

Meanwhile I rolled back Symphony **and** the extension to see if this has always been a background process issue. The answer is no. With the old code there are no...

I assume that the old version of creating a Symphony object has worked for me because it simply didn't include all the Symphony files, and so (by chance) it didn't...

Thanks for the pointers, I will do some more research. The cleanup function, however, will not see the sessions as empty (because they contain XSRF tokens).