Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I/O error spamming when no free disk space #7973

Closed
goto1134 opened this issue Dec 3, 2017 · 2 comments
Closed

I/O error spamming when no free disk space #7973

goto1134 opened this issue Dec 3, 2017 · 2 comments

Comments

@goto1134
Copy link

goto1134 commented Dec 3, 2017

qBittorrent version and Operating System

Windows 10 Pro version 1709 build 16299.64
qBittorrent version 4.0.1 (64-bit)

What is the problem

If there is I/O error that lasts for some time (in my case, it is that my disc filled), numerous I/O error popups appear. They are really annoying and coutinue to appear while the problem is still present.

What is the expected behavior

I would like to have one popup notification. In case of different kind of problems there can be more than one notifications. In case of the problem remains and notification is closed, it can be repeated, I think

Steps to reproduce

  1. fill the disk
  2. start downloading any torrent to the disk
@goto1134 goto1134 changed the title I/O error spamming I/O error spamming when no free disk space Dec 3, 2017
@asturel
Copy link

asturel commented Dec 3, 2017

dupe of #7649

@sledgehammer999
Copy link
Member

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.

@qbittorrent qbittorrent locked and limited conversation to collaborators Oct 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants