René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Memory Leak / OOM Crash during track changes","articleBody":"I am experiencing a significant memory leak in the BeefWeb plugin when managing a large playlist (approx. 11,000 tracks) on a headless Linux system. The deadbeef-main process grows by ~1.5MB to 2.5MB every time a track is skipped or the \"next\" command is issued. In my environment, this eventually leads to the Linux OOM killer terminating the process once it hits approximately 7.2GB RSS. \n\nEnvironment:\n\nOS: Linux (Ubuntu 24.04 / Mint 22.x)\n\nKernel: 6.x\n\nDeaDBeeF Version: 1.10.1\n\nBeefWeb Plugin Version: Feb 2025 build (approx. 2.7MB .so file)\n\nHardware: HP Elite 8300 SFF (8GB RAM) headless\n\nSteps to Reproduce:\n\nLoad a playlist with a large number of tracks (11,000 in my case).\n\nEnsure the BeefWeb plugin is active.\n\nMonitor the process memory usage: ps -o rss -p $(pgrep deadbeef).\n\nIssue several \"next\" commands via CLI: deadbeef --next.\n\nObserve that the RSS increases by 1-2MB per skip and does not plateau.\n\nAdditional Context:\nI have verified that this behavior is specific to the plugin. When the beefweb.so plugin is disabled/removed, skipping tracks in the same 11k-track playlist results in a stable RSS (~94MB to ~96MB) that does not continue to grow linearly. It appears the leak may be related to playlist serialization or metadata buffering triggered by track-change events and may not be limited to large playlists, even as this playlist size may have helped to reveal the memory leak.","author":{"url":"https://github.com/tommylicious","@type":"Person","name":"tommylicious"},"datePublished":"2026-05-05T11:57:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/368/beefweb/issues/368"}