From FreeMind

Revision as of 15:07, 25 May 2011 by Dan Polansky (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search



For troubleshooting on Linux, see FreeMind on Linux.


Not all issues that you encounter are a result of a bug in FreeMind. There may be a problem with your Java installation.

Java installation: You may need to check you Java installation, by entering a DOS console, and typing "java -version" to see whether Java is correctly installed and in what Java version.

Looking at error log: The first place to look at when you suspect a FreeMind bug is the error log. With FreeMind 0.8.0, run FreeMind from freemind.bat to see all the logged errors in the DOS console. With FreeMind 0.9.0 beta, the error log is a text file located at ".freemind" subfolder of your home folder; the name of the error log file is one of "log.0", "log.1", etc.

Java problems: To find out whether your problem is caused by Java virtual machine, you may try another Java Swing application, such as JEdit. If your problem is also shown by JEdit, it is more likely to be a Java one. Trying out the Eclipse development environment does not help, as Eclipse, although a Java application, is not a Swing application.

Please report bugs to SourceForge's Bug Tracker; see also Reporting bugs.


FreeMind is written in Java, a programming language whose executables need a virtual machine to run.

The official Java virtual machine is the one from Oracle, yet there are some other Java virtual machines. When FreeMind is run using another vitual machine than the one from Oracle, it may shows various glitches. One of the virtual machines that sometimes makes trouble is OpenJDK: see OpenJDK.

To check which Java virtual machine is installed on your computer, type "java -version" into a console of your operating system (MS DOS console in Windows, Bash terminal in Linux, and the like).

See also

Personal tools