apache2 crashed with SIGSEGV in zend_register_interfaces()

[ubuntu-bolivia]

none

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: apache2-bin 2.4.18-2ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Sun Aug 21 08:59:43 2016
ExecutablePath: /usr/sbin/apache2
InstallationDate: Installed on 2016-06-19 (64 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160618)
ProcCmdline: /usr/sbin/apache2 -k start
ProcEnviron:
 PATH=(custom, no user)
 LANG=C
Signal: 11
SourcePackage: apache2
StacktraceTop:
 zend_register_interfaces () from /usr/lib/apache2/modules/libphp7.0.so
 zend_register_default_classes () from /usr/lib/apache2/modules/libphp7.0.so
 zm_startup_core () from /usr/lib/apache2/modules/libphp7.0.so
 zend_startup_module_ex () from /usr/lib/apache2/modules/libphp7.0.so
 zend_hash_apply () from /usr/lib/apache2/modules/libphp7.0.so
Title: apache2 crashed with SIGSEGV in zend_register_interfaces()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 zend_register_interfaces () at /build/php7.0-zo7XM0/php7.0-7.0.8/Zend/zend_interfaces.c:565
 zend_register_default_classes () at /build/php7.0-zo7XM0/php7.0-7.0.8/Zend/zend_default_classes.c:33
 zm_startup_core (type=<optimized out>, module_number=<optimized out>) at /build/php7.0-zo7XM0/php7.0-7.0.8/Zend/zend_builtin_functions.c:340
 zend_startup_module_ex (module=0x55bbef3dad60) at /build/php7.0-zo7XM0/php7.0-7.0.8/Zend/zend_API.c:1849
 zend_hash_apply (ht=ht@entry=0x7f95c20e12a0 <module_registry>, apply_func=apply_func@entry=0x7f95c1d0aff0 <zend_startup_module_zval>) at /build/php7.0-zo7XM0/php7.0-7.0.8/Zend/zend_hash.c:1534

[Bryce Harrington (bryce)]

This crash occurs during server startup post-config parsing while attempting to bring up the php7.0's mod_php. It's having trouble registering the php interface.

I wonder if this is just an api incompatibility, such as if mod_php had been built for an older apache version or vice versa. If it is, then this same class of issue may still be relevant to currently supported versions, however for confirmation of that and for analysis purposes, we'd want a newly collected bug report. But since this is against an out-of-support version of Ubuntu I'm going to close it as expired. If anyone sees this same issue on 18.04 or 20.04 it would be quite helpful to have a fresh bug report filed on that.