dfens
Memory leak with quantum and processing binary files
Currently I have phoenix app which also schedules quantum jobs (GitHub - quantum-elixir/quantum-core: ⌚ Cron-like job scheduler for Elixir) with overlap: false mode
Jobs are importing & exporting relatively large json files.
Now my problem is
Leaking memory
This is current status and it will get worse since different/bigger data sets are going to be processed.
For example on start on the left app starts with ~60MB
Flat line in the end is after quantum job was processed
I did check also this memory management - Solving large binaries leak - Stack Overflow but forced gc / tuning ERL_FULLSWEEP_AFTER collect did not seem to help
If I run ImportTask/ExportTask on my local machine but not as quantum and observe memory - then I cannot reproduce this behaviour
Any tips welcome ![]()
Marked As Solved
NobbZ
Have you tried strings: :copy (assuming you use Jason)?
Also Liked
dfens
@NobbZ jackpot!
as the matter of fact I was using Jaxon for parsing since files were pretty big before. but just tested with Jason strings: :copy and issue does not occur anymore. I suspect this was misuse of Jaxon.stream on my side but I am completely satisfied with Jason results
@benwilson512 yes I did try, without any effect
Thank you so much for your input guys
NobbZ
From a quick glance it seems as if jaxon wasn’t copying and also did not provide an option to copy binaries.
You might still be able to use jaxon when you :binary.copy/1 strings it gives you manually.










