Problem with Java prevents Maple 10 and 11 from launching
It seems that the issue of the mathematics software Maple failing to launch is becoming epidemic around me, so I thought I should blog about it and its solution for further reference.
A week ago, I attended a case in which Maple 10 didn’t start: After clicking on its shortcut, Maple’s splash screen would pop up, linger for a few minutes and then go away, but Maple 10 itself wouldn’t show up. Maple’s process (maplew.exe) would show up in Processes tab of Task Manager and would not consume any CPU time.
Today, I attended a similar case in which Maple 11 didn’t start, only with significant difference: After clicking on its shortcut, an error message would instantly pop up: "Java Virtual Machine Launcher" "Could not create the Java virtual machine".
Maple’s technical support is well aware of these problems, which have a common cause, and has already published solutions in its knowledge base. These issues occur because Java Runtime, a very well-known component created by Sun Microsystems and used by Maple, does not behave properly on a system with an abundance of free memory available! (That’s right: When there is far more than enough memory!) The affected machines all had at least 2GB of memory installed.
The solution is to limit the amount of memory available to Maple. To do so:
- Close Maple by terminating "maplew" process. Use Task Manager or a similar tool to accomplish this.
- Open "launch.ini" file located in "bin.win" subfolder of Maple program folder with notepad or another text editor.
- Add a new line that says: maxheap=256m. If a such line already exist, make sure it is not preceded by a #. Also make sure the number to right of the equal sign is 256.
- Save the file.
- Run Maple.
Doing so will prevent Maple from using more than 256m of the free memory and will allow it to run normally. Maple tech support suggests to limit the memory to 700MB. However, I noticed that anything larger than 256MB on those machines was still troublesome. With these changes, however, Maple should launch without any problem.
Finally, I’d like to mention that another way to run Maple in such cases would be to run a number of other programs, thus reducing the amount of free memory available. This is, of course, neither a solution nor a workaround, but rather a technical warning: If you usually run Maple on systems with lots of free memory available along with a number of other programs, chances are that the issue remain hidden.
Have a nice day harnessing the power of mathematics!