Still having sporadic unresponsive issues.
Usually it happens when quickly updating or assigning labels to existing images. Sometimes it returns to a responsive state, other times I can wait overnight and still nothing.
The latest occurrence happened when I was modifying the stack and version settings in the preferences. I was done and clicked the OK button when the "wait" twirly appeared. After waiting about a minute, PSU suddenly closed. I checked in Performance Monitor and saw that IDImagerSU.exe is Suspended. It doesn't show in Task manager. Tried to Resume or End the process but nothing works. Had to Reboot to have a clean system.
If PSU is really just working on a long running process but not actually stuck, could it not put up a notification box or better a progress bar to that end? Would certainly save a lot of frustration.
Often even when PSU closes normally, it is still active in the Background Process window of Task Manager for some time. If I don't look in there and Reboot or Shutdown the computer, what if any database damage could happen?
Build 6576
sporadic unresponsive issues
Re: sporadic unresponsive issues
If you experience random "delays" then that typically points to the OS trying to reach disks. For instance, if your photo files are stored on a drive which goes into some "energy saving state" and then access to the drive is needed the the OS (Windows/macOS) needs to access the drive. The drive then needs to "wake up" which may cause delays as the OS needs to wait on the hardware, and PSU on its turn has to wait on the OS.
Another possible reason for unexpected waits is virus scanners. Some virus scanners are overly active and scan the temporary files that SQLite creates (WAL files) and while the virus scanner scans the file, SQLite has to wait for it, and as a result PSU has to wait. Always exclude the Catalog folder from any Virus scanner that you have installed. That also applies to the Virus Scanner that may come pre-installed with your OS (such as Windows Defender).
Having PSU running up to 30 seconds after closing it is not uncommon.
The chances of corrupting an SQLite database are slim, that's why SQLite is such a popular desktop database. You should only worry about corruption when SQLite is writing data to the database file and the file "suddenly disappears". That typically happens when you pull the plug while the computer is on, or a power failure occurs, or when you have the catalog files on a remote device which experiences connectivity issues. Hence, always keep the catalog files on an internal drive, never pull the power plug out of the outlet while the computer is on, and worry when a power failure occurs.
As for everything on the computer that we would regret losing it is important to always have a recent backup.
Another possible reason for unexpected waits is virus scanners. Some virus scanners are overly active and scan the temporary files that SQLite creates (WAL files) and while the virus scanner scans the file, SQLite has to wait for it, and as a result PSU has to wait. Always exclude the Catalog folder from any Virus scanner that you have installed. That also applies to the Virus Scanner that may come pre-installed with your OS (such as Windows Defender).
Having PSU running up to 30 seconds after closing it is not uncommon.
The chances of corrupting an SQLite database are slim, that's why SQLite is such a popular desktop database. You should only worry about corruption when SQLite is writing data to the database file and the file "suddenly disappears". That typically happens when you pull the plug while the computer is on, or a power failure occurs, or when you have the catalog files on a remote device which experiences connectivity issues. Hence, always keep the catalog files on an internal drive, never pull the power plug out of the outlet while the computer is on, and worry when a power failure occurs.
As for everything on the computer that we would regret losing it is important to always have a recent backup.
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: sporadic unresponsive issues
The images are on a networked TerraStation. During a PSu session, there should be enough activity to keep it awake.
The virus scanner has been told to ignore both the PSu app folder, the catalog folder, both on internal drives, as well as the external image drive.
Up to 30 seconds? hmmm, OK I usually do other things before closing the computer so I should be outside that window.
The computer is on a UPS so power failures should not be an issue and I do make backups, when i remember.
So was the crash to desktop while closing the Preferences window just a random event?
The virus scanner has been told to ignore both the PSu app folder, the catalog folder, both on internal drives, as well as the external image drive.
Up to 30 seconds? hmmm, OK I usually do other things before closing the computer so I should be outside that window.
The computer is on a UPS so power failures should not be an issue and I do make backups, when i remember.
So was the crash to desktop while closing the Preferences window just a random event?
Re: sporadic unresponsive issues
If your NAS (which is a typical device in Windows to show such delays) gives delays then the OS has to wait and PSU has to wait for the OS. Try if you also get delays when you dismount the shares to the NAS in Windows. Or switch PSU to "offline" mode, a mode where it won't interact with the file system.
Either way, this is not something any application has control over. Applications interact with the OS and that's it.
If crash occurs then typically you are asked to submit it. Always best to do so. If you can reliably reproduce a crash then best to report that to support@idimager.com. A crash that causes the application to disappear without the prompt to submit then that is not something that is (nor can be, as it no longer runs) recorded, hence the cause is unidentifiable.
Either way, this is not something any application has control over. Applications interact with the OS and that's it.
If crash occurs then typically you are asked to submit it. Always best to do so. If you can reliably reproduce a crash then best to report that to support@idimager.com. A crash that causes the application to disappear without the prompt to submit then that is not something that is (nor can be, as it no longer runs) recorded, hence the cause is unidentifiable.
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message