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

 ID:               49308
 Updated by:       and...@php.net
 Reported by:      f4ckm5 at web dot de
 Summary:          random crashes on freeing mysqli result storage
-Status:           Feedback
+Status:           Closed
 Type:             Bug
 Package:          MySQLi related
 Operating System: Windows Server 2003 SP2 32Bit
 PHP Version:      5.3, 6 (2009-08-22)
 Assigned To:      mysql

 New Comment:

Closing on reporter's request:



Sorry,



I would have used the bugtracking system, but the "retrieve
password"-function just gave me an empty page this evening...



Currently, I'm no longer involved in the project that gave us this
error. I'm not planning in getting involved again. Please feel free to
close the bug due to inactivity.


Previous Comments:
------------------------------------------------------------------------
[2010-04-08 18:04:26] and...@php.net

Checking if this thing is still alive. Do you get the same problem with
5.3.2?

Thanks!

------------------------------------------------------------------------
[2009-09-18 08:37:44] u...@php.net

Well, do you have any tips in what to do with the trace? Sorry, but a
reproducible case would be much more worth than the trace.



Alternatively, is it possible to enable the mysqlnd trace?

------------------------------------------------------------------------
[2009-08-29 15:31:34] f4ckm5 at web dot de

Do you have any tips on how to find the respective lines of code in a
70000 lines of code project which eventually cause the crash? All i can
see is the dying apache worker thread and the corresponding message in
the system log. And it is very annoying, that this happens only on the
productive system. No crashes on our development and test machines.

I would gladly provide a test script. Just tell me where to start
digging.

------------------------------------------------------------------------
[2009-08-26 15:38:34] u...@php.net

Any chance to provide a test script? I know its hard, but its also hard
to say anything based on the backtrace and without a reproducible test
case.



Thanks,

Ulf

------------------------------------------------------------------------
[2009-08-21 09:31:38] f4ckm5 at web dot de

I used the latest Snapshot 5.3.1-dev from Thu Aug 20 15:19:10 2009



The crashes became less frequent. Instead of 10 in 5 Minutes i caught
only 5 in 3.5 hours. But the crashes still occur:



#############################################################



Thread 250 - System ID 9828

Entry point   msvcrt!_endthreadex+2f 

Create time   21.08.2009 09:11:23 

Time spent in user mode   0 Days 0:0:0.171 

Time spent in kernel mode   0 Days 0:0:0.78 





Function     Arg 1     Arg 2     Arg 3   Source 

php5ts!_zend_mm_free_int+139     056cf838     00050004     00720336    

php5ts!_efree+36     012296e8     06894910     00725877    

php5ts!_zval_ptr_dtor+66     068948e4     006ad310     06868980    

php5ts!zend_hash_destroy+27     06876538     06868980     015a1665    

php5ts!zend_object_std_dtor+2b     06868980     056ce490     06868980   


php_mysqli!mysqli_objects_free_storage+25     06868980     056ce490    
05a733e4    

php_mysqli!mysqli_result_free_storage+28     06868980     056ce490    
056ce490    

php5ts!zend_objects_store_del_ref_by_handle_ex+1b6     0000002b    
015b1600     056ce490    

php5ts!zend_objects_store_del_ref+1e     06868960     056ce490    
00000000    

php5ts!_zval_dtor_func+76     06868960     00000000     05ab9050    

php5ts!ZEND_ASSIGN_SPEC_CV_VAR_HANDLER+237     0546fbfc     056ce490    
0546fe78    

php5ts!execute+29e     05ab9050     056ce400     00000000    

php5ts!zend_execute_scripts+f6     00000008     056ce490     00000000   


php5ts!php_execute_script+22d     0546fe78     056ce490     00000003   


php5apache2_2!php_handler+5d0     012c18b8     00615988     012c18b8   


libhttpd!ap_run_handler+21     012c18b8     012c18b8     012c18b8    

libhttpd!ap_invoke_handler+ae     00000000     012bc860     0546ff3c   


libhttpd!ap_die+29e     012c18b8     00000000     0065fb90    

libhttpd!ap_get_request_note+1ccc     012bc860     012bc860     012bc860
   

libhttpd!ap_run_process_connection+21     012bc860     0062b108    
0546ff84    

libhttpd!ap_process_connection+33     012bc860     012b1820     00000000
   

libhttpd!ap_regkey_value_remove+c7c     012bc858     00000000    
00000000    

msvcrt!_endthreadex+a3     012a7d08     00000000     00000000    

kernel32!BaseThreadStart+34     77b9b4bc     012a7d08     00000000    





PHP5TS!_ZEND_MM_FREE_INT+139In
httpd__PID__7192__Date__08_21_2009__Time_09_11_24AM__898__First chance
exception 0XC0000005.dmp the assembly instruction at
php5ts!_zend_mm_free_int+139 in C:\PHP\php5ts.dll from The PHP Group has
caused an access violation exception (0xC0000005) when trying to read
from memory location 0x02080174 on thread 250



Module Information 

Image Name: C:\PHP\php5ts.dll

Symbol Type:  PDB 

Base address: 0x006a0000

Time Stamp:  Thu Aug 20 15:19:10 2009  

Checksum: 0x00000000

Comments:   

COM DLL: False

Company Name:  The PHP Group 

ISAPIExtension: False

File Description:  PHP Script Interpreter 

ISAPIFilter: False

File Version:  5.3.1-dev 

Managed DLL: False

Internal Name:  PHP Script Interpreter 

VB DLL: False

Legal Copyright:  Copyright © 1997-2009 The PHP Group 

Loaded Image Name:  php5ts.dll

Legal Trademarks:  PHP 

Mapped Image Name:  C:\PHP\php5ts.dll

Original filename:  php5ts.dll 

Module name:  php5ts

Private Build:   

Single Threaded:  False

Product Name:  PHP 

Module Size:  5,45 MBytes

Product Version:  5.3.1-dev 

Symbol File Name:  C:\Dokumente und
Einstellungen\Administrator.HML\Desktop\php-debug-pack-5.3-win32-VC6-x86-latest\php5ts.pdb

Special Build:  &

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


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


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

Reply via email to