Edit report at http://bugs.php.net/bug.php?id=52083&edit=1
ID: 52083
Updated by: s...@php.net
Reported by: darylp at qualtrics dot com
Summary: Fatal Error "Call to a member function * on a
non-object" occurring randomly
-Status: Open
+Status: Closed
Type: Bug
Package: *General Issues
Operating System: CentOS 5.4
PHP Version: 5.3.2
-Assigned To:
+Assigned To: stas
Block user comment: N
Private report: N
New Comment:
This bug has been fixed in SVN.
Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
Thank you for the report, and for helping us make PHP better.
So marking as fixed then.
Previous Comments:
------------------------------------------------------------------------
[2010-10-07 22:54:31] darylp at qualtrics dot com
The development snapshot provided has been in place for two weeks on one
of our
production servers and we have not seen these errors since. We are
hesitant to put
a development snapshot on all of our production machines however. Is
there a
release schedule for PHP 5.3.4, and will the changes that fixed this bug
in the
development snapshot be released with it?
------------------------------------------------------------------------
[2010-09-13 20:06:18] darylp at qualtrics dot com
We attempted downgrading one of our production webservers to PHP 5.2.14
3-4 weeks
ago and haven't seen these errors since on that server. We continue to
see the
issue with our other webservers running PHP 5.3.2. I think that's a good
indication that the problem stems from the version upgrade. We will be
trying the
latest version on one of our servers as suggested.
------------------------------------------------------------------------
[2010-09-11 18:04:02] fel...@php.net
Please try using this snapshot:
http://snaps.php.net/php5.3-latest.tar.gz
For Windows:
http://windows.php.net/snapshots/
------------------------------------------------------------------------
[2010-06-22 23:27:26] darylp at qualtrics dot com
Unfortunately, this issue is occurring only in our production
environment and is
occurring sporadically. It is happening in 2-5 minute bursts on a single
server
and across different functions. For most of the other 24 hours those
scripts are
running, there are no problems. We have not been able to correlate the
times the
error occurs with any events on our servers or traffic load. We will
continue to
attempt to reliably reproduce this issue and submit code when available.
Are there
any other suggestions on testing to be able to reproduce this?
------------------------------------------------------------------------
[2010-06-15 16:04:25] pierr...@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves.
A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external
resources such as databases, etc. If the script requires a
database to demonstrate the issue, please make sure it creates
all necessary tables, stored procedures etc.
Please avoid embedding huge scripts into the report.
------------------------------------------------------------------------
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/bug.php?id=52083
--
Edit this bug report at http://bugs.php.net/bug.php?id=52083&edit=1
