microsoft / microsoft/AzureStorageExplorer
Linux Upgrade Fork Bomb
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Storage Explorer Version
1.45.0
Regression From
No response
Architecture
x64
Storage Explorer Build Number
20260730.9
Platform
All
OS Version
Zorin 18.1
Bug Description
Notification advertising a new version (1.46.0) is available. Hit open. Storage Explorer starts launching repeated downloads/extracts of the StorageExplorer.1.46.0.tar.gz in /tmp/{random folder number}. In Addition it forks a new running instance of Storage Explorer 1.4.5, this process repeats endlessly filling up /tmp storage and forking processes that fill memory.
Resource Types
No response
Authentication Method
Account name and key
Connection Type
Sign in (subscription)
Steps to Reproduce
- Launch Explorer (presumably in a Zorin Linux distribution, perhaps Ubuntu)
- Go to the Help menu and click Check for Updates.
- Wait for Notification to display at the top
- Select Open
- Scramble to terminate the multiplying instances
- Find delete multiple directories in /tmp
- Return to the old version.
Actual Experience
Storage Explorer processes start to proliferate.
/tmp storage starts filling up.
Expected Experience
A self-installing upgrade that works.
Additional Context
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the upgrade flow on Linux: use Help > Check for Updates, then select Open and observe the repeated launches and temporary downloads under /tmp. Read the system_info.txt attachment and inspect the update behavior associated with this entry point. Done means the upgrade launches a single instance, completes installation, and does not keep filling /tmp.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100