-
-
Notifications
You must be signed in to change notification settings - Fork 762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fatal Memory Error #81
Comments
Woa, there's a lot of memory being used there. Do you know which specific version you were using yesterday? Does that version work if you install that specific version again? Do you backup significantly more files than yesterday? Or bigger files? Do you have any more info that'll allow me to recreate your issue? |
Thanks for the quick reply. It works in 3.0.4 but fails in 3.0.5 (I just tested by reverting back to 3.0.4). No significant file changes from yesterday or very large files.
|
Two more tidbits:
|
One more question before I dive deep into this: what's your Laravel version? |
Laravel Framework version 5.2.22 |
Total backup size for successful backup of 7921 files = 179.7 MB |
Could you try updating to the latest version? Could you look inside the directory you want to backup if there are any hidden directories (starting with a dot) that you don't want to back up? |
Seems to be working well using the newest version + PHP 7. Will continue to monitor and update the issue if anything comes up. Thanks. |
Cool, reopen this issue if anything new comes up. |
The backup process is failing after performing a composer update today (3/9/2016). The same configuration was working fine yesterday (3/8/2016) before composer update. I am backing up many files as I have a standalone Laravel app installed on my server for laravel-backup that is backing up four domains (three of which are Laravel apps).
The text was updated successfully, but these errors were encountered: