starred/koel-koel

Fork 0

mirror of https://github.com/koel/koel.git synced 2026-04-25 16:56:02 +03:00

[GH-ISSUE #768] Import memory error #555

New issue

Closed

opened 2026-02-26 02:33:32 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 02:33:32 +03:00

Owner

Originally created by @NickBusey on GitHub (Jul 18, 2018).
Original GitHub issue: https://github.com/koel/koel/issues/768

Hey, thanks for contributing to Koel! To save time for both of us, please make sure these checkboxes are checked before submitting the issue:

You have read and followed closely the Wiki, Upgrade Guide, as well as Troubleshooting
The issue has not been reported before
This is not a "how to install on Windows" or "why is my npm messed up" question
You're a cool person

All checked? Now also make sure your issue

Is associated with a version. Or better yet, a commit.
Is as detailed as possible (ahem... OS, browser, steps to reproduce, maybe?)
Includes the error output if it's a bug/error report ("Whoops!" is not very helpful, you know)
Is in English, 因为我不说中文。

v3.7.2 via 0xcaff/koel

Trying to import via php artisan koel:sync -v and getting the following error:

 3966/6478 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░░]  61% 16 minsGangstas Paradise.mp3 has no changes – ignoring

In getid3.php line 1724:

  Allowed memory size of 134217728 bytes exhausted (tried to allocate 33554464 bytes)

Originally created by @NickBusey on GitHub (Jul 18, 2018). Original GitHub issue: https://github.com/koel/koel/issues/768 Hey, thanks for contributing to Koel! To save time for both of us, please make sure these checkboxes are checked before submitting the issue: - [x] You have read and followed closely the [Wiki](https://koel.phanan.net/docs), [Upgrade Guide](https://github.com/phanan/koel/releases), as well as [Troubleshooting](https://koel.phanan.net/docs/#/troubleshooting) - [x] The issue has not been reported before - [x] This is not a "how to install on Windows" or "why is my npm messed up" question - [x] You're a cool person All checked? Now also make sure your issue - [x] Is associated with a version. Or better yet, a commit. - [x] Is as detailed as possible (ahem... OS, browser, steps to reproduce, maybe?) - [x] Includes the error output if it's a bug/error report ("Whoops!" is not very helpful, you know) - [x] Is in English, 因为我不说中文。 v3.7.2 via 0xcaff/koel Trying to import via `php artisan koel:sync -v` and getting the following error: ``` 3966/6478 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░░] 61% 16 minsGangstas Paradise.mp3 has no changes – ignoring In getid3.php line 1724: Allowed memory size of 134217728 bytes exhausted (tried to allocate 33554464 bytes) ```

kerem closed this issue

2026-02-26 02:33:32 +03:00

kerem commented

2026-02-26 02:33:32 +03:00

Author

Owner

@phanan commented on GitHub (Jul 19, 2018):

Just increase your memory limit.

@phanan commented on GitHub (Jul 19, 2018): Just increase your memory limit.

kerem commented

2026-02-26 02:33:32 +03:00

Author

Owner

@NickBusey commented on GitHub (Jul 20, 2018):

Sure that's one solution, but what if my library was twice the size, increase it more? I think an incremental import would be nice, read in 100 files, save them to the DB, clear the memory, read in 100 more, etc.

@NickBusey commented on GitHub (Jul 20, 2018): Sure that's one solution, but what if my library was twice the size, increase it more? I think an incremental import would be nice, read in 100 files, save them to the DB, clear the memory, read in 100 more, etc.

kerem commented

2026-02-26 02:33:32 +03:00

Author

Owner

@phanan commented on GitHub (Jul 20, 2018):

Indeed, incremental scanning/importing is a good idea.

On Fri, 20 Jul 2018 at 02:27, Nick Busey notifications@github.com wrote:

Sure that's one solution, but what if my library was twice the size,
increase it more? I think an incremental import would be nice, read in 100
files, save them to the DB, clear the memory, read in 100 more, etc.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/768#issuecomment-406453173, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHrt0hC7SloIKiIqOsKK6hV9sMhcmmCeks5uISPcgaJpZM4VU5VS
.

@phanan commented on GitHub (Jul 20, 2018): Indeed, incremental scanning/importing is a good idea. On Fri, 20 Jul 2018 at 02:27, Nick Busey <notifications@github.com> wrote: > Sure that's one solution, but what if my library was twice the size, > increase it more? I think an incremental import would be nice, read in 100 > files, save them to the DB, clear the memory, read in 100 more, etc. > > — > You are receiving this because you modified the open/close state. > Reply to this email directly, view it on GitHub > <https://github.com/phanan/koel/issues/768#issuecomment-406453173>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AHrt0hC7SloIKiIqOsKK6hV9sMhcmmCeks5uISPcgaJpZM4VU5VS> > . >

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#555

No description provided.

Rows
Columns