Reporting Bugs

[Bhikkhu Pesala]

Users should not change the prefix. A moderator will change the status as the bug report progresses.

1. Reported — New threads in the Bug Report forum will have this default prefix. It means that the program behaves in a way that is not expected.
2. Confirmed — Another user has followed the recipe given in the report and has confirmed that it also happens on his/her computer.
3. Forwarded — The confirmed report has been forwarded to Irfan by email
4. Pending — A reply has been received from Irfan. He knows about the bug, so there is nothing more that users need to do.
5. Fixed — The bug has been fixed and will be available in the next official release, or perhaps in a bug-fix version in our downloads area
6. No Bug — Strictly speaking, faulty behaviour is not always a bug. For example, a lot of plugins were never designed to work with 64-bit so the fact that they do not work is not a bug. 64-bit plugins need to be written by someone.

Please help us by posting in the right forum.

A bug is something that happens that was not intended by the programmer. If the program crashes or freezes, that is usually a bug.

1. If the program now behaves differently than it used to, that is not usually a bug.
2. If the program doesn't behave as you think it should, that is not a bug.
3. If you don't know how to use the program, that is not a bug.
4. Performance issues may be caused by bugs, but are often just that you're asking your CPU and RAM to do too much. Turning off resampling and undo will solve some problems.

When reporting bugs, please give:

1. Your Operating System, and IrfanView version number.
2. Your hardware specification
3. A clear step-by-step recipe to reproduce the bug reliably. Without this, no one can confirm the bug, and no one can fix a bug that cannot be reproduced.
4. A screenshot or error message, if it is relevant
5. A problematic file that causes the crash or error message, or a link to such a file.

[Bhikkhu Pesala]

I just banned one user for six months for flooding the forum with bug reports for known issues, e.g. plugins do not work with 64-bit version. The IrfanView 64-bit page clearly states:

Advantages of IrfanView 32-bit over 64-bit version:

• Runs on a 32-bit and 64-bit Windows
• Loads all files/images for normal needs (max. RAM size is about 1.3 GB)
• Needs less disc space
• All PlugIns will work: not all PlugIns are ported (yet) to 64-bit (like OCR) and some 32-bit PlugIns must be still used in the 64-bit version, some with limitations (see the "Plugins32" folder)
• Slideshows created on 64-bit IrfanView will not run in 32-bit Windows (not stated on the website)
• Some old 32-bit PlugIns (like RIOT and Adobe 8BF PlugIn) work only in compatilibilty mode in IrfanView-64
• Command line options for scanning (/scan etc.) work only in 32-bit (because no 64-bit TWAIN drivers)

We welcome genuine bug reports, and we do our best to test them. If you're not satisfied with the resolution of a bug or the lack of any resolution feel free to contact Irfan Skiljan directly. We are all just users here, and this site is not owned nor administered by Irfan Skiljan.

Users submitting bug reports here should submit a bug report themselves to Irfan Skiljan (see the Help menu in IrfanView for his email). Anyone can submit bug reports; it is not the duty of moderators to do it for you, but do tell us that you submitted a report and what reply you received so that we can update the thread's status.