Severe problem of all versions is inability to save the worksheet during non-stopable computations (including mserver crashes which are usual upon an external call crash). In this case Maple application cannot be closed normally. The "save" button is clickable but the worksheet is not saved. Fortunately, some versions of Maple save the current version of the worksheet as .sav file, but unfortunately that file is incomplete (the last section is missing). There are two solutions. The first is to backup every couple of minutes. The second is as follows: 1) Make sure that .sav file is generated; 2) Kill all Maple programs; 3) Rename .sav and _MAS files otherwise they will be overwritten next time you open your worksheet in Maple. 4) Use the last saved version of the worksheet or _MAS file as your restore point. 5) Use .sav file to copy the last-minute changes if any.

Maple 14-17 bugs and problems

List of detected problems

• Error command inside loops can destroy Maple kernel [example].
• For _EnvLegendreCut=1..infinity, which is the standard choice for physical applications, Maple incorrectly evaluates Legendre functions [example].
• Incorrect evaluation of the complementary elliptic function of the third kind [example].
• Erroneous symbolic integration [example].
• Eigenvectors command fails for symbolic matrices [example].
• Blocks recognition in GraphTheory package fails, see example of TwoEdgeConnectedComponents command [example].
• Bug in save/read commands [example].
• Bug in FileTools[Binary][Write] command [example].
• Bug in evalhf command [example].
• Plot option "filled" produces vertical streaks.
• If you run an external program using ssystem command and that programs becomes suspended, Maple becomes suspended too, not allowing you to save the worksheet.
• ExcelTools[Import] command creates empty example.log file in current directory.
• Some plots, e.g. dualaxisplot, cannot be saved in a Maple worksheet (when reopened Maple tells that the worksheet is incomplete) [example].
• Tickmarks settings are ignored sometimes [example].
• KernelDensity estimators crash if the variable 'x' is initialized [example].
• Erroneous multiplication with Hermitian matrix [example].

List of bugs for Maple 2025

• Wrong graph traversal [example].

Limitations

(to the best of my knowledge of Maple)

• Optimization package cannot compute the gradient numerically [example].
• Most of the commands from XMLTools package are useless when dealing with "real-world" xml-files, the rest of the commands are inefficient/inconvenient.
• There is no way to access the local variables of your procedure from the outside [example].
• Limited unevaluation tools [example].
• Module inheritance is not supported. You cannot even duplicate an existing module.
• Restart is needed to "unwith" a non-package module. The latter is needed when you need to access the module variables.
• Limited debugging tools. Let you have a cumbersome procedure and you have misprinted a name or have forgotten to declare it. Fortran will tell you that you have undeclared variable. Maple may decide that it is the global variable and you have to find your bug by yourself.
• Multithreading does not work [example].
• Use of unprotected names as parameters makes the code vulnerable [example].
• Tables and other objects whose name is a pointer are not protected by protect command.
• The scanf command cannot scan "1.234D-05".
• Maple continue to execute the Execution Group after an error, and there is no way to change this unusual behavior.
• Z-order cannot be set: curves are always on top of filled regions.
• Every mw-worksheet contains at least 50 Kb of redundant information, mainly style definitions.