[GH-ISSUE #268] PHP Memory Exhausted #198

Closed
opened 2026-02-26 02:32:24 +03:00 by kerem · 5 comments
Owner

Originally created by @alex-phillips on GitHub (Mar 16, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/268

Running koel v2.2.0 on a Mac Mini server running OS X 10.10.5 with PHP7 (installed through Homebrew).

I am having an issue when running the syncscript where PHP runs out of memory after a while. The following is the error presented when it fatals:

Koel syncing started. All we need now is just a little patience…
PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 67108896 bytes) in /Users/exonintrendo/www/koel/vendor/james-heinrich/getid3/getid3/getid3.php on line 1694


  [Symfony\Component\Debug\Exception\FatalErrorException]
  Allowed memory size of 134217728 bytes exhausted (tried to allocate 67108896 bytes)

It's quite possible that it could be due to the size of my library, but not entirely sure. My iTunes library is currently reporting 43,101 items.

Originally created by @alex-phillips on GitHub (Mar 16, 2016). Original GitHub issue: https://github.com/koel/koel/issues/268 Running koel v2.2.0 on a Mac Mini server running OS X 10.10.5 with PHP7 (installed through Homebrew). I am having an issue when running the `sync`script where PHP runs out of memory after a while. The following is the error presented when it fatals: ``` Koel syncing started. All we need now is just a little patience… PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 67108896 bytes) in /Users/exonintrendo/www/koel/vendor/james-heinrich/getid3/getid3/getid3.php on line 1694 [Symfony\Component\Debug\Exception\FatalErrorException] Allowed memory size of 134217728 bytes exhausted (tried to allocate 67108896 bytes) ``` It's quite possible that it could be due to the size of my library, but not entirely sure. My iTunes library is currently reporting 43,101 items.
kerem closed this issue 2026-02-26 02:32:25 +03:00
Author
Owner

@phanan commented on GitHub (Mar 17, 2016):

Try increasing your PHP memory limit.

<!-- gh-comment-id:197730098 --> @phanan commented on GitHub (Mar 17, 2016): Try increasing your PHP memory limit.
Author
Owner

@alex-phillips commented on GitHub (Mar 17, 2016):

I understand increasing the memory is a solution, but I was hoping for some insight on what exactly is causing the memory to run out. And to what end increasing it going to solve?

Is this issue associated with the size of my library? Will I have to keep increasing the allowed memory usage as my media library grows over time?

<!-- gh-comment-id:197838380 --> @alex-phillips commented on GitHub (Mar 17, 2016): I understand increasing the memory is a solution, but I was hoping for some insight on what exactly is causing the memory to run out. And to what end increasing it going to solve? Is this issue associated with the size of my library? Will I have to keep increasing the allowed memory usage as my media library grows over time?
Author
Owner

@phanan commented on GitHub (Mar 17, 2016):

During sync, Koel reads your media files and tries to extract data from
them. This process consumes memory.
Now in your case, 134217728 bytes is only 128MB, which is really low,
especially when you have your own server. I'd suggest a 512MB setting.
And no, you don't have to keep increasing the memory, as syncing is
incremental – only new or changed files are read.

On Thu, Mar 17, 2016 at 7:36 PM, Alex Phillips notifications@github.com
wrote:

I understand increasing the memory is a solution, but I was hoping for
some insight on what exactly is causing the memory to run out. And to what
end increasing it going to solve?

Is this issue associated with the size of my library? Will I have to keep
increasing the allowed memory usage as my media library grows over time?


You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/phanan/koel/issues/268#issuecomment-197838380

<!-- gh-comment-id:197852204 --> @phanan commented on GitHub (Mar 17, 2016): During sync, Koel reads your media files and tries to extract data from them. This process consumes memory. Now in your case, 134217728 bytes is only 128MB, which is really low, especially when you have your own server. I'd suggest a 512MB setting. And no, you don't have to keep increasing the memory, as syncing is incremental – only new or changed files are read. On Thu, Mar 17, 2016 at 7:36 PM, Alex Phillips notifications@github.com wrote: > I understand increasing the memory is a solution, but I was hoping for > some insight on what exactly is causing the memory to run out. And to what > end increasing it going to solve? > > Is this issue associated with the size of my library? Will I have to keep > increasing the allowed memory usage as my media library grows over time? > > — > You are receiving this because you modified the open/close state. > Reply to this email directly or view it on GitHub > https://github.com/phanan/koel/issues/268#issuecomment-197838380
Author
Owner

@alex-phillips commented on GitHub (Mar 17, 2016):

Thanks for the information, makes much more sense now.

<!-- gh-comment-id:197872968 --> @alex-phillips commented on GitHub (Mar 17, 2016): Thanks for the information, makes much more sense now.
Author
Owner

@My1 commented on GitHub (May 28, 2016):

I would say that this should get into the wiki.
also maybe an error note should be set on the page instead of "unknown" error when setting the path.

<!-- gh-comment-id:222324702 --> @My1 commented on GitHub (May 28, 2016): I would say that this should get into the wiki. also maybe an error note should be set on the page instead of "unknown" error when setting the path.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#198
No description provided.