Bug #13173 Updated: no gc even when gc_probablity = 100

ID: 13173 Updated by: yohgaki Reported By: php-jp@typhoon.co.jp Old Status: Open Status: Feedback Bug Type: Session related Operating System: FreeBSD 4.X PHP Version: 4.0.6 and 4.10 New Comment: What kind of user session handler you have? You have reported Bug ID: 13078 also. Don't paste script, but please explain a bit. Also have to check your httpd and php error log? Is there anything interesting? Previous Comments: ------------------------------------------------------------------------ [2001-12-13 02:52:41] php-jp@typhoon.co.jp Just tried this with 4.1.0 and found that the problem has not been resolved. ---ends--- ------------------------------------------------------------------------ [2001-09-06 07:09:24] php-jp@typhoon.co.jp settings in php.ini: session.save_handler = files session.gc_probability = 100 session.gc_maxlifetime = 120 Problem: User1 was assigned session_id()=somesessionid01. Session variables are saved properly. User1 bookmarked the page. If NO ONE else has visited the site and started another session, then User1 can return and revive the session no matter how much time is passed (over the gc_maxlifetime value,) when he/she visits the pages again with an URL like: http://site.site.site/some.php?SID=somesessionid01 However, if another user visits the site, gets another session id, e.g. somesessionid02 BEFORE User1 returns with the said URL, then, garbage collection occurs and data are deleted properly. Conclusion: Garbage collection is *not* done when the same session_id returns BEFORE another session_id is generated. This happens when the session.save_handler = files However if: session.save_handler = user where 'user' is a customized handler, the relevant sess_gc routine is called properly and gc is taken care of. ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=13173&edit=1