Bug 953883 - Segfault on PHP 5.4.* and php-pecl-apc-3.1.14-1.fc18 or php-pecl-apc-3.1.15-0.2.svn329724 with Magento
Summary: Segfault on PHP 5.4.* and php-pecl-apc-3.1.14-1.fc18 or php-pecl-apc-3.1.15-0...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: php-apc
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Chris Chabot
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-19 12:19 UTC by Philippe
Modified: 2014-02-05 20:42 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 20:42:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Philippe 2013-04-19 12:19:55 UTC
Description of problem:
Apache error_log shows AH00052: child pid XX exit signal Segmentation fault (11)
 
[:error] [pid 27639] [client X.Y.Z.T:44082] PHP Fatal error:  Cannot override final method Mage_Core_Model_Abstract::clearInstance() in /var/www/vhosts/rendezvousdeco.com/httpdocs/app/code/core/Mage/Catalog/Model/Product.php on line 38, referer: ...
[:error] [pid 26567] [client X.Y.Z.T:44079] PHP Fatal error:  Cannot override final method Mage_Core_Model_Abstract::clearInstance() in /var/www/vhosts/rendezvousdeco.com/httpdocs/app/code/core/Mage/Catalog/Model/Product.php on line 38, referer: ...

Setting apc.enable_opcode_cache=0 would stop the problem from occuring.
Also disabling Magento apc cache usage in local.xml would stop the problem.

Version-Release number of selected component (if applicable):
Occurs on :
httpd-2.4.4-2/php-5.4.13-1/php-pecl-apc-3.1.15-0.2.svn329724
httpd-2.4.3-15/php-5.4.11-1/php-pecl-apc-3.1.15-0.2.svn329724
happens also on a lot more versions (even on Fedora 17 with apache 2.2 + latest apc package available in the distribution)

IMPORTANT NOTE : the problem does NOT occur on Fedora 15 with
httpd-2.2.22-1.fc15/php-pecl-apc-3.1.9-1.fc15/php-5.3.13-1.fc15

How reproducible:
At this time i did not find a way to reproduce it at will but it occurs frequently in production hence i had to disable apc.

This issue looks a bit like https://bugs.php.net/bug.php?id=63005
or https://bugs.php.net/bug.php?id=63497 but nothing sure.

Any help will be greatly appreciated.
Regards,
Philippe

Comment 1 Fedora End Of Life 2013-12-21 12:53:51 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2014-02-05 20:42:48 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.