While in nearly all cases crash is considered a bug (you should report it to Bookmap and we'll try to fix it in next versions), there are few cases where it happens due to external reasons, and removing those will let bookmap run normally.
Windows messing up directory ownership
We have observed a situation where Windows can suddenly change ownership of files in a way that will make those inaccessible to your account. This is rare, but this will cause bookmap to crash, as it suddenly has no access to it's own files.
When this happens you will see a stack trace starting with something like this:
java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native
java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Pointer
This usually means that Windows changed ownership of the following folder:
C:\Users\<your user name>\AppData\Local\Temp\jna-<some number>
(note, that some folders in the path are hidden, so you'll have to make windows show hidden files first)
Just close bookmap and delete or rename that folder. This will require admin permissions, so windows will ask you about that. After getting rid of the folder and starting bookmap again new one should be created and Bookmap should be back to normal.
Running out of disk space
There are many reasons why it might happen, one being that Bookmap itself needs quite a lot of space for the cache when operating for a long time without restarts or refreshes. Bookmap currently does not handle that situation gracefully - it will attempt writing something to disk and crash. Solution is simply freeing more disk space.
In general - running out of disk space is something you should avoid regardless of Bookmap - a lot of software doesn't handle it very well, and as you get closer to 0 free space filesystem performance also degrades (btw, many SSD will also start operating slower when there is little space left, so you might want to always have 15-20% free)
Video driver issues
Bookmap utilizes OpenGL for performance reasons. While we try to detect unsupported configurations, sometimes it fails and Bookmap tries to use the rendering which doesn't really work. You can recognize this by either of:
- Chart looking weird, like having white areas, etc
- Bookmap freezing instead of showing the chart
- Bookmap crashing instead of showing the chart
When this happens you can turn off GPU acceleration from the Settings menu. If it helps - this was related to video driver. Now, turning off GPU accelerations costs a lot of CPU power and disables some minor features, so you might want to try fixing the underlying cause. Often simply installing the latest driver from your GPU manufacturer is the only thing you need to do.
Bookmap will not run if:
- you don't have a 64 bit OS (older versions will try to run, but won't work very well). We've seen cases where high end computers had 32 bit OS installed - don't do that (you also lose all the memory above 4GiB, sometimes even more).
- you have a very old OS (like Windows XP).
You might have troubles if:
- you are running an older OS version, like Windows Vista or Windows 7. We try to support those, but it is not our primary focus, and we slowly phase those out.
- you don't have much RAM, to a point where it can crash in some use cases. Bookmap ideally needs 3-4GiB to itself, and it will only allocate that much if you have 16+ GiB (you can change that in settings, but allocating too much memory on lower end machines will negatively affect performance)