You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm, not that I'm aware of! I haven't really studied the Julia GC or allocation system in depth yet myself. All the allocations in Air, I believe, are either made via the copy() function or are just plain constructor allocations. Nor does Air ever call the GC nor deallocate memory itself.
Probably not related, but I recall noticing during tests that the GC could get temporarily pretty slow if you performed a lot of small allocations and deletions in one go (e.g., by building up a PDict from a very large Dict one key-value pair at a time). This isn't really a surprise, though; I mostly just noticed that it seemed to perform worse with these small allocations than the JVM did under a similar task. I haven't seen any crashes like this.
Let me know if I can be of any help with debugging this!
As seen on PkgEval https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_hash/ff8b327_vs_29ea1fe/Air.1.8.0-DEV-593ff735b36.log
Before I dive in to see if this is a JuliaLang proper bug, are you doing anything interesting with memory?
The text was updated successfully, but these errors were encountered: