Lurker terminated with 'OOMKilled' event about securecodebox HOT 5 CLOSED

Had a look at the code, had this falsely remember it is loading the entire file in memory.
Should hopefully be easy to change / fix it to avoid these issues alltogether.

I don't quit agree that making this configurable is the best fix for it. That would just be one additional thing people would need to tweak to ensure the systems works properly, I'd rather try to see if we can avoid the issue alltogether.

That being said, of course having the resources for the lurker be configurable should still be possible, just think we should ensure that the default is working properly, vene for large files.

from securecodebox.

Hi @J12934 , Yes seems like it resolved the issue, thank you !
I will close this :)

from securecodebox.

HI @Alon-Katz

Do you know how big the file is that it's trying to upload there?

The lurker should stream the upload and never load the complete file into memory, so I don't know where this would happen.
We been using the lurker with these resource limits for a ton of scans and never ran into this issues even when uploading some really big files.

from securecodebox.

Hi @J12934 , The file size was 20.6 MB, and the issue is reproduced each time.
I believe the best option here is to allow customization of the lurker resources.

from securecodebox.

Should be fixed with release v4.5.0 :)
Can you check if this resolves the issue for you?

from securecodebox.