Bug #51091 [Com]: Persistent PDO Connections Crash

From: Date: Mon, 27 Dec 2010 22:05:29 +0000
Subject: Bug #51091 [Com]: Persistent PDO Connections Crash
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-157344@lists.php.net to get a copy of this message
Edit report at http://bugs.php.net/bug.php?id=51091&edit=1

 ID:                 51091
 Comment by:         lsmith@php.net
 Reported by:        achristianson at yakabod dot com
 Summary:            Persistent PDO Connections Crash
 Status:             Closed
 Type:               Bug
 Package:            Reproducible crash
 Operating System:   CentOS 5.4
 PHP Version:        5.3.1
 Assigned To:        dmitry
 Block user comment: N
 Private report:     N

 New Comment:

I should add that I have only seen this issue when running my entire
test suite on 
the CLI. Running the crashing unit tests individually makes the issue go
away.


Previous Comments:
------------------------------------------------------------------------
[2010-12-27 23:03:57] lsmith@php.net

I am also seeing segfaults/bus errors, which go away after disabling GC
on PHP 
5.3.4 using PostgreSQL via Doctrine 2.0. Though the issues only appeared
when I 
added ext intl. I am seeing these issues on OSX and Debian.

------------------------------------------------------------------------
[2010-10-12 00:50:57] felipe@php.net

I can't reproduce this as well. (probably already fixed...)

------------------------------------------------------------------------
[2010-09-10 00:01:21] matth+php at mlalonde dot net

For the record, we are using Doctrine 2.0 (which uses the PDO) and
PostgreSQL.

------------------------------------------------------------------------
[2010-09-09 23:54:58] matth+php at mlalonde dot net

I can replicate under Ubuntu Server LTS 10.04 running nginx and php-fcgi
(using spawn fcgi).

Reading symbols from /usr/lib/gconv/ISO8859-1.so...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/gconv/ISO8859-1.so
Core was generated by `/usr/bin/php5-cgi'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000000006b2ea9 in gc_zval_possible_root (zv=0x4c7d018) at
/build/buildd/php5-5.3.2/Zend/zend_gc.c:143
143	/build/buildd/php5-5.3.2/Zend/zend_gc.c: No such file or directory.
	in /build/buildd/php5-5.3.2/Zend/zend_gc.c
(gdb) bt
#0  0x00000000006b2ea9 in gc_zval_possible_root (zv=0x4c7d018) at
/build/buildd/php5-5.3.2/Zend/zend_gc.c:143
#1  0x00000000006a1698 in zend_hash_destroy (ht=0x4c7ce20) at
/build/buildd/php5-5.3.2/Zend/zend_hash.c:726
#2  0x000000000054e1ed in sxe_object_free_storage (object=0x4c7bcc0) at
/build/buildd/php5-5.3.2/ext/simplexml/simplexml.c:2016
#3  0x00000000006b9aec in zend_objects_store_free_object_storage
(objects=0xd8fd18) at
/build/buildd/php5-5.3.2/Zend/zend_objects_API.c:92
#4  0x0000000000688ac5 in shutdown_executor () at
/build/buildd/php5-5.3.2/Zend/zend_execute_API.c:302
#5  0x00000000006953e2 in zend_deactivate () at
/build/buildd/php5-5.3.2/Zend/zend.c:962
#6  0x0000000000641095 in php_request_shutdown (dummy=0x4c7d018) at
/build/buildd/php5-5.3.2/main/main.c:1649
#7  0x0000000000722550 in main (argc=32767, argv=0x0) at
/build/buildd/php5-5.3.2/sapi/cgi/cgi_main.c:2160

------------------------------------------------------------------------
[2010-06-28 05:15:54] dxm007 at gmail dot com

Hi, I've been trying to setup Menalto Gallery and after I got through
entire setup 
of a fresh installation (to verify php, MSSQL, IIS were working fine), I
pointed 
the gallery to my existing database and flat files.  Because my data
came from an 
older version of the Gallery, it invokes upgrade wizard which dies every
single 
time on step 2.  I've created a crash dump with adplus and it appears to
be 
exactly the same bug as what's reported here.

This is 100% repeatable on my machine.  I'm using PHP 5.3.2 with Windows
2008 
Server R2, IIS7 and MSSQL 2008 R2.  I've also been able to get past the
crash by 
adding "zend.enable_gc = Off" to php.ini

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


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=51091


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


Thread (15 messages)

« previous php.bugs (#157344) next »