ID: 25916 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: Open Bug Type: Scripting Engine problem Operating System: Solaris 9 PHP Version: 4.3.4RC1 New Comment:
[EMAIL PROTECTED]: When you give feedback, set hte status to Open!!! Previous Comments: ------------------------------------------------------------------------ [2003-11-19 11:04:15] [EMAIL PROTECTED] There are no special things to do. But the interesting thing is the following: since i replaced get_browser() by get_browser($_SERVER['HTTP_USER_AGENT']) it does not seem to crash anymore. So there must be some problem with reading the $_SERVER superglobal in the extension. But I am not sure, just a hint. ------------------------------------------------------------------------ [2003-11-19 10:57:16] [EMAIL PROTECTED] The browscap extension definitely leaks, but as far as I know, it's only during module startup/shutdown, and it's been like that since forever. I've never seen it blow up like this, but I can try to reproduce on Solaris 8 with iPlanet. Is there anything special that needs to be done besides hammering the test script with requests? I've been meaning to take another look at the browscap stuff, that extension has kind of been disowned... J ------------------------------------------------------------------------ [2003-11-19 03:29:37] [EMAIL PROTECTED] Yes I would like to do that. Could be a memory leak. I followed the discussion. But these fixes are for PHP5 only! ------------------------------------------------------------------------ [2003-11-17 18:33:08] [EMAIL PROTECTED] mr. Richards posted some patch(es) to internals@ to fix some ZTS related issues. Maybe you should try those? ------------------------------------------------------------------------ [2003-10-20 04:30:58] [EMAIL PROTECTED] Addendum: It is not a problem with wrong extension dir in php.ini (because all extensions are linked static) like in other bugs. The configuration phpinfo() can be found at: http://134.1.2.11/test.php ------------------------------------------------------------------------ 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/25916 -- Edit this bug report at http://bugs.php.net/?id=25916&edit=1
