-
Bug
-
Resolution: Fixed
-
Major
-
2.5
-
MOODLE_25_STABLE
-
MOODLE_26_STABLE
-
w31_
MDL-39430_m26_opcache -
Discovered from MDL-36060, eaccelerator doesn't support closures - a critical php 5.3 feature. Its also the way the php api is moving (if you could ever suggest a direction for php..)
https://github.com/eaccelerator/eaccelerator/issues/12
That feature is nearly 4 years old and that bug has been dead like that for nearly 10 months, which highly suggests eaccerator development is dead.
Unfortunately, eaccerator used to be much better than APC in the opcode cache world and so I imagine there are a lot of moodle sites using it.
I think that we should start with a warning and then also potentially drop support of eaccelerator (if we can detect it, not certain of that). If they aren't supporting anything as critical as closures, who knows what else could break.
- caused a regression
-
MDL-40952 Don't cause notices on phpunit runs without opcache
- Closed
- has a non-specific relationship to
-
MDL-40415 OPcache support
- Closed
- has been marked as being related by
-
MDL-39754 Decide Moodle 2.6 requirements and push them to environment.xml
- Closed
- is blocked by
-
MDL-40679 Add zlib as a recommended component to environment.xml (for 2.6 and up)
- Closed
- will be (partly) resolved by
-
MDL-40554 opcache support (backport of MDL-40415)
- Closed
- will help resolve
-
MDL-25412 Call to undefined function redirect_if_major_upgrade_required()
- Closed
-
MDL-29863 Fatal error: Class 'context' not found
- Closed
-
MDL-36060 mod/lti brings Invalid opcode 153/1/8 with eaccelerator
- Closed
-
MDL-39432 Closures within the course renderer cause fatal errors when using eAccelerator
- Closed
-
MDL-39577 APC/PHP fatal error: unable to obtain pthread lock (EDEADLK)
- Closed