ID: 43579 Updated by: [EMAIL PROTECTED] Reported By: assid at assid dot com Status: Open Bug Type: Session related Operating System: Debian etch PHP Version: 5.2.5 New Comment:
The libdl stuff can be ignored, so that looks like a clean valgrind run. But, are you sure the problem happens on the command line? I'd run the entire apache -X through valgrind. You'd need to do it on a quiet machine somewhere that isn't getting hit, of course, so you can control the requests you send to it while valgrind is running. Hit it until you see the problem, then stop and show us that valgrind output from that. Previous Comments: ------------------------------------------------------------------------ [2008-02-28 11:40:49] assid at assid dot com Okay ran valgrind (as far as i can understand it) http://assid.com/valgrind.txt I have removed some extensions as i was still testing, but to no success. I hope the log proves useful to you. ------------------------------------------------------------------------ [2008-02-28 10:54:02] assid at assid dot com Still trying to remove more extensions and test. Rasmus, I have sent you a private email with 2 links to video files, which shows the phpmyadmin bugs. It seems the bugs faced are infact more indepth as you suggested. I do apologize for private mailing btw., but since they are links to videos, I didnt want to post them in public. ------------------------------------------------------------------------ [2008-02-28 09:20:14] assid at assid dot com 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. ------------------------------------------------------------------------ [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. ------------------------------------------------------------------------ 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
