-
Notifications
You must be signed in to change notification settings - Fork 296
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
The program closes with an error when opening any file #410
Comments
Affected by this same issue on fully updated Arch and WEASIS 4.1.0 The only information I can add is that at startup Weasis logs that it is using Java 20.0.1 while on my system |
Installed a new version of Java: But it had no effect. The program still closes. |
I have the same problem. I am using Ubuntu 22.04.2 LTS and installed the deb package from the website -weasis_4.1.0-1_amd64.deb. |
It seems there is a problem with OpenGL in Weasis. I observed the similar crashes while was testing Weasis 4.1.0 in Windows 10 virtual system on Virtualbox. With switched off 3D acceleration everything worked as expected. When I tried to switch on 3D, Weasis crashed on loading study. |
There is no need to install Java because it is packaged in the application. The problem is related to a native library compiled in a static way. The problem is quite strange because it does not occur on all systems (works for me on Ubuntu 22.04 but not on version 20.04). The problem is difficult to identify because it does not trigger a fatal error log and by compiling the library in debug the problem does not occur. When I deactivate the 3D module, I have no errors although there is no link with the library that triggers the "invalid pointers"! Here is how to disable the module while waiting for a fix:
|
Besides the possible OpenGL issues, it maybe kind of side effects of using latest Java and therefore latest build tools for building Java. My custom built Weasis for Windows (Java 20.0.1+9, Microsoft VS 2022) works fine on updated Windows 10, but fails to load DICOMDIR on original Windows LTSC 2019 and Windows 7. Just did nothing with nothing in log, even without any 3D support. |
I confirm, with the 3D module disabled when changing values in the file ~/.weasis/data/weasis-core/persistence.properties: |
Same problem here, with the latest RPM installed in Fedora 36, when trying to load a DICOMDIR from a CD, the program crashes. Starting from command line only gives the following output (last lines):
|
I built a new deb and rpm package with a Snapshot version (is not kept in the cache at boot time). To reactivate the 3D module, you can remove the 2 properties from the file ~/.weasis/data/weasis-core/persistence.properties:
Please tell me if this solves the crash problem. The new package is less portable on all distributions because it has 2 new dependencies. |
The new update launches and works great! 3D Viewer works too. |
I confirm that v4.1.1-SNAPSHOT works without this bug |
Thank you for your feedback. @Sergey-5000 This is the first time I've seen a crash in relation to the memory. I think it's more related to a driver problem because the memory management is not limited to the GPU. See this post. @AlexZaka VirtualBox does not allow to have a functional 3D driver (even if sometimes it seems to be the case, it remains very experimental). However it works very well with VMware and Nvidia GRID. |
Please check the GitHub issues system, the forum and/or this website first to see if your problem has not been reported yet.
Describe the bug
When opening any DICOM or jpg file, the program closes
To Reproduce
Steps to reproduce the behavior:
Expected behavior
In version 4.0.3, everything was open and you could work. Expectations in the new version are the same...
Desktop (please complete the following information):
Additional context
deb, snap, flatpak give the same result.
"free(): invalid pointer"
Screenshots
If applicable, add screenshots to help explain your problem.
Traces
If applicable, add log files from Weasis or from the DICOM archive.
report.txt
The text was updated successfully, but these errors were encountered: