evrial

Yes running latest edge with default settings: App version: v3.0.2-edge Also had issue on v3 stable. Node process takes ~800Mb-1500Mb of Resident size (RES) Indexing: ``` docker stats MEM USAGE...

1. Happening with indexing and other jobs in sequence. But gif format conversion taking forever 2. Limited to 5G, working as expected, no OOM or any errors Looking at BLOCK...

I was able to isolate the bug. I have a large folder of pictures, 116 GB, 65k images. All indexed, reindexing job is instant and zero memory consumed. If I...

Yep I limited the container memory with these settings and working as expected, when hitting 3G, the GC releases memory: ``` deploy: resources: limits: # Hard limit: The container cannot...

Yeah I'm thinking maybe writing pseudo-gallery just to develop intuition and benchmark the most performant and reasonable solution. Then port the code into Pigallery (hardest part for me).

> Now diagnostics says: `11/30/2025, 11:26:54 AM[DEBUG][ConfigDiagnostics] Garbage collector is not available, the app won't be able to manually trigger it to save RAM.` Hmm I couldn't get this message...

Gemini response: --- You have correctly identified that the warning must be originating from within the file access operations in `DiskManager.ts`, which calls functions in this `MetadataLoader.ts` file. After reviewing...

Found the root cause https://github.com/MikeKovarik/exifr/blob/6cbf6e921688faf7723e1f2e0b9e672d1f0aa21c/src/file-readers/FsReader.mjs#L44

Exifr follow up: --- You've hit the nail on the head\! This file, `FsReader.mjs`, which is part of the `exifr` library, is the **direct source** of the `DeprecationWarning` regarding the...

I made a PR for exifr but unlikely this will get into upstream, so what do we do? https://github.com/MikeKovarik/exifr/pull/137