ID:               27978
 Updated by:       [EMAIL PROTECTED]
 Reported By:      megan dot boardman at rweinnogy dot com
-Status:           Open
+Status:           Bogus
 Bug Type:         Reproducible crash
 Operating System: UNIX 5.1 ALPHA
 PHP Version:      4.3.5
 New Comment:

This report is as useful as not reporting anything. Please come up with
SOLID reproducing script and how to reproduce.

(and note: We don't have any access to any alpha machines..aren't those
some relic anyway? Get new machine? :)




Previous Comments:
------------------------------------------------------------------------

[2004-04-13 10:01:35] megan dot boardman at rweinnogy dot com

Description:
------------
Since upgrading to PHP 4 have been experiencing problems with Apache
1.3.26 periodically appearing to crash.  This has gradually gotten
worse as we have worked our way up through the 4.x generation of PHP. 



Timeline goes as follows (based on messages in Apache error_log):



- PHP 4.0.4pl1 gave occasional child XXXX exit signal Segmentation
Fault (11).



- PHP 4.1.2 gave no errors.



- PHP 4.3.3, 4.3.4 and 4.3.5 gave frequent child XXXXX exit signal
Abort (6) errors



This PHP script is being used to submit requests to a database.  This
"aborting" behaviour appears to be causing the sending web browser to
lose contact with Apache, and hence send the form post multiple times. 
The PHP script always appears to get as far as sending the submission
to the database, but then falls over before sending the response back
to the web server.  Result -> multiple duplicate database submissions,
occasional "Page Not Found" 505 errors in the web browser.



Working with an Oracle 8 database and mod_fastcgi 2.2.12

Reproduce code:
---------------
Cannot easily reproduce code, however general form is as follows:



1) Create object that contains contents of HTML page being constructed



2) Pass object by reference to function



3) Function builds database submission (based on variables that have
been POSTed by a previous web form submision) and then sends an email,
sets a cookie and builds HTML based on result from database.



4) Function ends and web page printed to screen



- DB Submission always happens

- Email always happens

- Apache appears to fall over before the cookie gets set and before the
HTML gets displayed



NOTE:

- Seems order invarient.

- Methodology applied for earlier webforms posts, and works without
multiple submissions.



Expected result:
----------------
- DB Submission 

- Email to be sent

- Cookie set in browser

- Resultant HTML posted to screen

Actual result:
--------------
- DB submission

- Email sent

- Cookie & HTML display do NOT necessarily occur


------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=27978&edit=1

Reply via email to