ID: 43579 User updated by: assid at assid dot com Reported By: assid at assid dot com -Status: Feedback +Status: Open Bug Type: Session related Operating System: Debian etch PHP Version: 5.2.5 New Comment:
Any suggestions on the options / how to use valgrind without learning the whole thing. Perhaps the cli cmd to run ? I am starting to think this isnt limited to session related. phpMyAdmin as i mentioned starts acting very very strangely here. Due to the lack of knowledge of valgrind, i can try and see if i can try removing an extension to see if it makes any difference, while retaining atleast the basic ones that i DO need. If i can get the valgrind options (exact cli commands ) to use, that would be great. Previous Comments: ------------------------------------------------------------------------ [2008-02-28 06:07:18] [EMAIL PROTECTED] 4 different people on our end have tried to reproduce this without any success. And no, those memory issues you refer to have nothing to do with this since they were fixed long before that snapshot you tried. At this point you'll need to dig in yourself. Fire up Valgrind and see if you can spot what might be causing the corruption. It could be in some extension that we don't have in any of our environments here. It definitely isn't the session code itself, so it is impossible to diagnose without more information. ------------------------------------------------------------------------ [2008-02-27 08:19:03] jsnyxx at gmail dot com Hi Rasmus Yes, we can confirm that nothing changed on the box apart from php 5.2.4 -> 5.2.5. We found it easier to reproduce the bug once XCache was installed, but the bug still exists even when we remove Xcache, it's just more intermitment. The developer of Xcache thinks this is related to a heap corruption of some sort. See here: http://forum.lighttpd.net/topic/42805 The issue for us seems to be that even though the session file exists on the server (under a private /sessions directory), at some point when the browser sends the cookie with the PHPSESSID header, the server seems to temporarily "lose" the information stored in the session file and returns a blank _$SESSION variable. However, after a few more refreshes it provides the correct info from the $_SESSION variable again. ------------------------------------------------------------------------ [2008-02-26 09:32:06] assid at assid dot com Yes, same machine, same everything. Even phpmyadmin dies on me. I just had to move it back. I can apachectl stop; make install; apachectl start ; whenever your online. Since its a production box, i need functionality to work fine, so i moved it back down to 5.2.4 As I said i am available on freenode as Assid ------------------------------------------------------------------------ [2008-02-26 09:11:13] [EMAIL PROTECTED] There is only a single trivial change to the session extension between 5.2.4 and 5.2.5 and it was to fix http://bugs.php.net/42596 The change is here: http://cvs.php.net/viewvc.cgi/php-src/ext/session/mod_files.c?r1=1.100.2.3.2.9&r2=1.100.2.3.2.10&pathrev=PHP_5_2&diff_format=u I don't see how this change could have caused these problems. Could you please verify that 5.2.4 works under the exact same conditions that 5.2.5 doesn't work? That is, on the same machine, built the same way and running the same code. ------------------------------------------------------------------------ [2008-02-26 08:27:56] assid at assid dot com Hrm, strange, i dont use xcache. But yeah session integrity is messed up. Looks like we gotta wait for 5.2.6 and hope the developers fixed that bug. It does seem php5.2-200802241730 is still not done, as a matter of fact, the session file in -dev seems to disappear, whereas atleast in 5.2.5 it remains. (very little testing in -dev btw). So its gone from bad to worse. - Data integrity ? - Another important note, is that phpmyadmin acts super strange as well. The css i believe is generated on the fly, that goes awry and sql queries start yielding no results. I am not sure if this is session related. or not! ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/43579 -- Edit this bug report at http://bugs.php.net/?id=43579&edit=1
