FatalErrorException not shown in bugsnag about bugsnag-laravel HOT 9 CLOSED

It is not possible in PHP to catch an out of memory exception:

from bugsnag-laravel.

I'm not sure why this is happening yet. It looks like bugsnag-php should be able to catch memory errors, but there may be some interaction with laravel I've missed.

If you'd like to debug the problem further, help would be greatly appreciated, otherwise we'll get round to this during the next week or so.

from bugsnag-laravel.

As of Laravel 5 this can be fixed by adding Bugsnag::notifyException($e); in the report method of the custom exception handler bundled with Laravel in app/Exceptions/Handler.php

from bugsnag-laravel.

@onbjerg 👍

@ConradIrwin this should definitely be on the readme file.

from bugsnag-laravel.

This is fixed in Laravel 5, which we now support!

from bugsnag-laravel.

What about Laravel 4? no support anymore? :(

from bugsnag-laravel.

@brayann Use an older version of the package.

from bugsnag-laravel.

@brayann See the legacy integration docs here: https://docs.bugsnag.com/platforms/php/laravel/legacy/

from bugsnag-laravel.

@duncanhewett I was asking about the fix for the memory limit error

from bugsnag-laravel.