Serialization of 'Closure' is not allowed

Question

I have a custom Exception handler in my code (which used to work properly), until suddenly I saw this error yesterday:

PHP Fatal error:  Uncaught exception 'Exception' with message 'Serialization of 'Closure' is not allowed' in /raid0/nginx/www/voiceportal/lib/logutils.php:34 Stack trace:
#0 /raid0/nginx/www/voiceportal/lib/logutils.php(34): serialize(Array)
#1 [internal function]: custom_exception_handler(Object(AMQPConnectionException))
#2 {main}

I read that it can be caused if an anonymous function is tried to be serialized, but this is what threw the error for me:

//logutils.php
function custom_exception_handler($exception) {
   $trace_id = uniqid();
   $trace = serialize(array('trace_id' => $trace_id, 'trace' => $exception->getTrace()));
   ...
}

Not sure if it was caused by trying to serialize getTrace(), but if I remember correctly, it used to work earlier.

The original exception was (as seen in the trace) AMQPConnectionException.

I am trying to understand what caused the 'Serialization of Closure not allowed' exception.

Thanks!

I don't know what exception occurred in the main code, so don't know that. — shyam, Mar 16 '14 at 07:52
I don't understand your problem. You have to provide more details — hindmost, Mar 16 '14 at 07:57
So the original exception was an AMQPConnectionException. More details added to the question. — shyam, Mar 16 '14 at 08:15
You have to show full body of `custom_exception_handler` as well as the code catching this exception — hindmost, Mar 16 '14 at 08:31

score 2 · Accepted Answer · edited May 23 '17 at 10:30

PHP's backtrace structure includes a reference to the object whose method is being called at each level of the stack. When it tries to serialize the trace, any objects which reference closures (or reference objects which themselves reference closures and so on) will prevent serialization.

In your case, you can re-cast the trace into a slightly less descriptive form or find which objects contain closures and either repackage the closures as __invoke instances or skip them when serializing by implementing Serializable, as described here. Your choice here would depend on what you're doing with the trace. If it's only meant to a be human-readable description of what went wrong, consider using the getTraceAsString() method instead of getTrace().

score 1 · Answer 2 · answered Mar 06 '15 at 17:27

I've written a function that allows any Exception to be serialized. This is done by flattening complex values in the backtrace.

Source:

https://gist.github.com/Thinkscape/805ba8b91cdce6bcaf7c

Usage:

//logutils.php
function custom_exception_handler($exception) {
   flattenExceptionBacktrace($exception); // <---- ADD THIS
   $trace_id = uniqid();
   $trace = serialize(array('trace_id' => $trace_id, 'trace' => $exception->getTrace()));
   ...
}

score 0 · Answer 3 · answered Jun 14 '17 at 11:21

0

I know this is old topic, but I would like to recommend my own library to serializing stack traces. Object $stackTrace can contain values and can be serialized. Unserialized object will contain only custom dumps of variables (@see interface).

answered Jun 14 '17 at 11:21

bkrukowski

56
3

Serialization of 'Closure' is not allowed

3 Answers3

Source:

Usage: