[BUG] Deleting files appears to start a work processor task for every file

[kruton]

Bug Report

Description

When deleting multiple files from a bucket (e.g., a directory containing multiple files), the console appears to start a new work queue processor for every file selected. So if you have 2000 files you're deleting, it will start 2000 work queue processors. Each of the work queue processors will check every second whether it can start deleting another file. The browser's tab CPU usage will go above 100% in this case until the deletion is done.

At the end of the deletion processing, you'll get 2000 messages in console of "⏸️ Task manager not started, skipping queue processing"

Steps to Reproduce

1. Go to Browser
2. Click on any bucket to browse
3. Select (checkmark on left) a directory with many files in it (technically you can see it with just 2 files)
4. Click "Delete selected"
5. Confirm deletion
6. Look at Javascript console for duplicated messages (also see CPU spike if the number of files being deleted is large)

Expected Behavior

A single work queue should be sufficient. It will be able to add tasks for all the 2000 files.

Actual Behavior

2000 work queue processors are started up and they all race to add new files onto a small queue.

Environment

• OS: macOS
• Browser: Chrome
• Node.js: Unknown
• Package version: 2025-10-23T05:59:57Z@1.0.0-alpha.65

Error Details

7CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
84CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
55CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
24CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
4CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
81CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
53CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
180CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
41CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
10CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
9CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
98CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
56CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing
283CpCdiNJX.js:38 ⏸️ Task manager not started, skipping queue processing

Additional Context

Checklist

• I have searched existing issues to ensure this is not a duplicate
• I have included steps to reproduce
• I have tested in the latest version

[cxymds]

Hi, Bro. you’ll need to upgrade your RustFS to the latest version. I noticed that the log output you shared is from an earlier version.