How to resolve Bad Allocation error in GALILEOS Viewer?

Question

Good afternoon! Could you please advise how to resolve this error? The disk contains discs with an executable file with CT scans. When launching this file, the loading process takes a long time, after which an error appears System Exception bad allocation. We tried increasing the computer's paging file size and freed up space on the C: drive so that there is 25 GB of free space, but the error persists. The RAM is 16 GB. Could you please suggest what might be causing this issue?

Answer 1

As for resolving the "Bad Allocation" error in the GALILEOS Viewer, it appears to be related to memory allocation issues. Here are a few suggestions to try and resolve this issue:

1. Check for Software Updates: Ensure that the GALILEOS Viewer software is up to date. Sometimes updating the software can resolve memory management issues.

2. Increase Virtual Memory: You've already increased the paging file size, but ensure it is set optimally. You can try increasing it further to see if it helps.

3. Close Unnecessary Applications: Close any unnecessary programs running in the background to free up more RAM for the GALILEOS Viewer.

4. Check for Corrupted Files: The executable file or the CT scan files might be corrupted. Verify the integrity of these files, if possible.

5. Reinstall the Software: Consider uninstalling and then reinstalling the GALILEOS Viewer software. This can sometimes resolve issues related to corrupted files or settings.

6. Contact Support: If none of the above solutions work, it might be best to contact the software’s support team for further assistance.

7. Hardware Upgrade: If you are still encountering issues, consider a RAM upgrade, although with 16 GB, this is unlikely to be the primary issue unless handling extremely large data sets.

Using these steps, you might be able to resolve the "Bad Allocation" error and run the GALILEOS Viewer successfully.

Answer 2

You will not be able to open "large" size images through Galileos, Sirona devices can take old images in low resolution, and new ones in high resolution. So the program for unloading "Large" images runs without errors, but immediately after unloading it does not work even if you try to open it on the computer that just created it. This is a bug in the program that is related to the amount of data that the "large" image contains, which causes a memory allocation error and subsequent program crash. At the moment, there is no solution to this problem and it is unlikely to appear. I advise you to ask the clinic that took the image to send it in the "sidexis viewer" format, or you need to send the patient to make image in "small" format.