-
Notifications
You must be signed in to change notification settings - Fork 214
OOM with prerelease version #3999
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
@amrgetment thanks for running with the extra logging. I was hoping to see some output like "Asset graph size: ", but I don't see that in the output you just posted? "Failed after 23m" ... 23m is huge, is that normal? i.e. did it take that long before? A sample repro would be fantastic. I'll anyway see if I can figure something out, and update here if I do. Thanks a lot for your help :) |
23m is too much, it should be like minutes or so |
@amrgetment I tried a bunch of big (1000 file) examples using Are you using any other generators I should throw into the mix? Another random question: is your code in one package, or does it split across multiple packages? I'll keep trying things: I'm close to releasing the new version so any random testing I can do is useful. Looking forward to that repro :) |
I use a lot of generators:
My code is in a single package |
My project almost covered all generators 😅 |
Thanks! I'll take a look at them all. So far I added auto_route_generator, nothing suspicious yet. I uploaded new version 15e775f which logs which generator is running, that might give us a clue :) |
@amrgetment Great news! I have a repro :) No idea yet what triggered it, but I managed to hit a state where it gets stuck with RAM usage climbing forever until it fails with OOM. So hopefully, no need for you to spend time on a repro now. I will update here once I either have a fix, or have failed to find one :) |
So it is not related to a specific generator, great 👍 , Good Luck |
I think those logs need to be a part of |
@davidmorgan It seems to be working fine and no memory issue
|
Re: where the time is going, I plan to add logging that should make that clearer, before releasing :) that way any feedback will be considerably more useful. |
Discovered here
#3834 (reply in thread)
The text was updated successfully, but these errors were encountered: