php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #68998 Wincache Crash in allocate_memory during wincache_resolve_path
Submitted: 2015-02-06 17:00 UTC Modified: 2015-07-16 18:17 UTC
Votes:3
Avg. Score:4.7 ± 0.5
Reproduced:3 of 3 (100.0%)
Same Version:1 (33.3%)
Same OS:3 (100.0%)
From: tser at deltacontrols dot com Assigned: ericsten (profile)
Status: Closed Package: WinCache (PECL)
PHP Version: 5.4.37 OS: Window Server 2012
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: tser at deltacontrols dot com
New email:
PHP Version: OS:

 

 [2015-02-06 17:00 UTC] tser at deltacontrols dot com
Description:
------------
Using WinCache 1.3.6.3.
Notice a number of error message regarding abandoned mutex

[05-Feb-2015 07:34:14 America/Vancouver] PHP Fatal error:  WINCACHE: lock_writelock: acquired abandoned mutex RESPATHS_SEGMENT_1_0_113638_X. Something bad happend in another process! in C:\Program Files (x86)\Delta Controls\enteliWEB\website\library\Zend\Loader.php on line 134

which indicates one of the php-cgi process crash with the Mutex locked.

From timestamp, able to find the crash dump.
See call stack below

Test script:
---------------
It happen randomly. No test script to demonstrates the bug.

I have the crash dump but not sure how to attach to the bug.
Please advise.

Expected result:
----------------
No crash

Actual result:
--------------
 	php_wincache.dll!allocate_memory(alloc_context * palloc=0x026613e8, unsigned int size=51581140, void * * ppaddr=0x0173cff0) Line 179	C
 	php_wincache.dll!alloc_smalloc(alloc_context * palloc=0x026613e8, unsigned int size=556) Line 1046	C
 	php_wincache.dll!create_rplist_data(rplist_context * pcache=0x026715a0, const char * filename=0x11dae138, const char * cwdcexec=0x0173d060, rplist_value * * ppvalue=0x0173d054) Line 128	C
 	php_wincache.dll!rplist_getentry(rplist_context * pcache=0x026715a0, const char * filename=0x11dae138, rplist_value * * ppvalue=0x0173d2a8, unsigned int * poffset=0x0173d2b4) Line 627	C
 	php_wincache.dll!aplist_fcache_get(aplist_context * pcache=0x0266c850, const char * filename=0x11dae138, unsigned char usesopen='\0', char * * ppfullpath=0x0173d318, fcache_value * * ppvalue=0x0173d31c) Line 1761	C
>	php_wincache.dll!wincache_resolve_path(const char * filename=0x0266c850, int filename_len=299557176) Line 1202	C


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2015-02-06 19:10 UTC] ericsten@php.net
-Assigned To: +Assigned To: ericsten
 [2015-02-24 23:06 UTC] stefan dot kolloch at loocka dot de
same error here, using PHP 5.5.8

stopping apppool and starting apppool solves it temporarily, Server 2012 R2
 [2015-07-16 18:17 UTC] ericsten@php.net
-Status: Assigned +Status: Closed
 [2015-07-16 18:17 UTC] ericsten@php.net
Fixed in WinCache 1.3.7.6.  The error message was un-actionable, and caused users angst and much gnashing of teeth.  Removed message and converted to ETW event for separate tracking.
 [2015-11-24 14:42 UTC] derek at groupmail dot io
We also get this issue - we're running Wordpress 4.3.1 with PHP 5.5.11.0 and WinCache 1.3.6.3 on an Microsoft Azure Virtual machine (Windows Server 2012 with IIS 8.5). 

We got this error yesterday:-

[23-Nov-2015 19:03:12 UTC] PHP Fatal error:  WINCACHE: lock_writelock: acquired abandoned mutex FILELIST_SEGMENT_1_0_291026_X. Something bad happend in another process! in C:\inetpub\siteroot\xxxxxxxxxxxxxxxx\wp-content\plugins\formidable\formidable.php on line 54

So, can you tell me is this issue actually fixed in WinCache 1.3.7.6 (as indicated in the comments below) or is this new version just logging the issue out to a different place (ETW event for separate tracking)? i.e. Is it worth upgrading the WinCache to 1.3.7.6 - will it cure the issue?

Thanks!
Derek.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Apr 18 17:01:28 2024 UTC