|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #76980 Interface gets skipped if autoloader throws an exception
Submitted: 2018-10-06 21:38 UTC Modified: 2018-10-09 12:13 UTC
Avg. Score:4.1 ± 0.9
Reproduced:8 of 12 (66.7%)
Same Version:8 (100.0%)
Same OS:5 (62.5%)
From: martin at auswoeger dot com Assigned:
Status: Verified Package: Scripting Engine problem
PHP Version: 7.2.10 OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
Solve the problem:
10 + 9 = ?
Subscribe to this entry?

 [2018-10-06 21:38 UTC] martin at auswoeger dot com
If a class implements an interface for which the registered autoloader throws an exception, the class is actually defined afterwards but without the interface.

Test script:

spl_autoload_register(function ($class) {
    if ('Foo' === $class) {
        class Foo implements Foointerface {}
    } elseif ('Foointerface' === $class) {
        throw new Exception();

try {
    // First call triggers the autoloader
    new Foo();
} catch (Exception $e) {}

// For the second call Foo is loaded
var_dump(new Foo());

// Even though it’s missing the interface
var_dump(new Foo() instanceof Foointerface);
var_dump((new ReflectionClass('Foo'))->getInterfaces());

Expected result:
Fatal error: Uncaught Exception in …  
thrown in … on line 7

Actual result:
object(Foo)#3 (0) {
array(0) {


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2018-10-06 21:56 UTC]
What's the expected *behavior* here? That Foo should not be defined at all since the interface couldn't be loaded? And the second "load" of Foo trigger the autoloader again and raise the exception again?
I think the way it works now is fine: Foo could be mostly defined except the interface, there was no other problem with it, and PHP was quite happy to raise an exception which you totally ignored. At least this way the code has a chance of working.

Or what if the exception was actually an Error? It's semantics, but that way you wouldn't accidentally catch it.
 [2018-10-06 22:17 UTC]
> What's the expected *behavior* here? That Foo should not be defined at all since the interface couldn't be loaded?

Yes, that would be the expected behavior.

Master has some changes that should make it easier to correctly handle this. Right now the code segfaults though.
 [2018-10-06 22:24 UTC] martin at auswoeger dot com
A partial loaded class is very confusing I think. Most developers probably wouldn’t expect that a class can be loaded without its interfaces.

> What's the expected *behavior* here?

If you change the above test script from `implements` to `extends` it behaves as I would expect it.

There is also a Symfony bug report that shows a real world use case where this behavior was unexpected and causes issues: <>
 [2018-10-07 01:28 UTC] a at b dot c dot de
Allowing the creation of class Foo to go ahead even if its interface failed to autoload would also bite users who use type declarations in function signatures.

function dowithfoo(Foointerface $foo)

dowithfoo(new Foo());
 [2018-10-09 12:13 UTC]
-Status: Open +Status: Verified -Package: *General Issues +Package: Scripting Engine problem
 [2018-10-09 12:13 UTC]
For reference: <>
PHP Copyright © 2001-2018 The PHP Group
All rights reserved.
Last updated: Wed Dec 19 01:01:27 2018 UTC