harababurel/gcsf

Out of memory: Killed process xxxx (gcsf)

Open

#77 opened on Mar 31, 2020

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Rust (2,378 stars) (94 forks)user submission
help wanted

Description

While copying large (4GB) file from mounted folder to my local disk I am seeing OOM kill.

Looks like gcsf is keeping all files in memory. I tried reducing values of cache_max_seconds , cache_max_items and cache_statfs_seconds but noo luck.

Contributor guide

Tech stack
rust
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Rust programmingFUSE filesystem basicsmemory profiling tools
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate memory usage during large file reads. Examine the caching mechanism in the source code, particularly in files like `src/cache.rs` or similar. Use Rust's memory profiling tools or valgrind to identify allocations that persist during sequential reads. Look for any unbounded caching that does not respect cache size limits.