Mathematica Stack Exchange is a question and answer site for users of Mathematica. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The problem I am about to ask has appeared once here: Memory Leak in Frontend - anyone know a workaround?. However, in this question I would like to put it in a bit different context.

Problem recipe:

  • Set $HistoryLength to 0 (this forces mathematica not to keep any history of evaluations)
  • Create a graphic object, which contains many colors/opacities/primitives/pointsizes/...
  • Open system monitor in your operational system
  • Rasterize the object in mathematica
  • Export it (optional), clear all the variables
  • Check your system monitor: memory used by mathematica frontend has grown larger

Example of the problem:

This example is not minimal, but is aesthetically appealing. Following the recipe, first set the history length:

$HistoryLength = 0; 

Then create a graphic object. In this case, it is a set of approx 0.5 10^4 points, having random positions inside a 0.5 radius sphere, random sizes and random colors, following some colorscheme. A cylinder is added afterwards to make the object look like a tree.

PointNumber = 10^4;
BushSize = 0.5;
PointLocations = 
  Select[(2 BushSize {Random[], Random[], Random[]} - {0.5, 0.5, 
        0.5}) & /@ Range[PointNumber], Norm[#] < BushSize &];
PointNumber2 = Length[PointLocations];
PointSizes = 0.01 Random[] & /@ Range[PointNumber2];
PointColors = 
  ColorData["PlumColors"][Random[]] & /@ Range[PointNumber2];
GraphicObject = 
  MapThread[{#1, PointSize[#2], Point[#3]} &, {PointColors, 
    PointSizes, PointLocations}];

Now, open the system monitor and rasterize everything:

TreeStuff = 
  Graphics3D[{Opacity[0.8], Brown, EdgeForm[], 
    Cylinder[{{0, 0, -1}, {0, 0, 0.1}}, 0.01], GraphicObject}, 
   PlotRange -> {{-1, 1}, {-1, 1}, {-1, 1}}, ImageSize -> 600, 
   Boxed -> False]]

As you can see, mathematica front-end has expanded in size by some 50 Mb! It is not all, at all. If you reevaluate the notebook, mathematica will pick another set of random points and will expand in the memory again. However, if you re-rasterize an object which has been rasterized before, memory will not be leaked.


The described behavior is clearly a bug. Say, one is producing an animation. If a given frame has been rasterized and saved, no information needs to be stored about it in the memory. Nevertheless, it gets stored incrementally.

It seems hard to imagine, that nobody has ever created complex graphics with mathematica before. In particular, in processing datasets or in creating animations, one has to rasterize such graphics many times. In this case, if the parameters of graphics change, mathematica takes all the system memory. Therefore, at least somebody, making complex graphics with mathematica, must have faced a similar problem before.

What do people commonly do to treat this issue? How can one clear the frontend memory, which expands so obviously in system monitor after each new evaluation of the above presented code?


The code outputs this pretty tree: enter image description here

share|improve this question
Beautiful tree indeed :) – Öskå Sep 15 '13 at 22:10
Thank you! In fact, it is rather easy to generalize the code, so that it generates a grove of a given shape, with grass and clouds. – Alexey Bobrick Sep 15 '13 at 22:12
@AlexeyBobrick Or you can use built-in stuff to create a stupid scene :P – R. M. Sep 16 '13 at 2:06
You're right, other people do have problems with producing large graphics. :) Sometimes they're mentioned on the site (eg this Q&A). Other users report possible memory leaks. – cormullion Sep 16 '13 at 8:42
@rm-rf : I once were making galactic dynamical simulations, where I put Beethoven into the center. Looked rather inspiring. – Alexey Bobrick Sep 16 '13 at 11:42

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.