I came across a possible memory leak while playing with 3.2.0 today.
I was in my library (which is huge) continually altering a certain subnetwork, changing colors, shapes, etc. Each change took a second or so to render.
Things went fine for awhile and then the rendering started to slow. Then I could no longer pan in either pane and the dreaded beachball appeared. When I tried to save my work I got memory errors like this:
I was unable to save and finally had to force quit, losing my work. I don't recall anything like this happening under similar circumstances under 3.0.52.
Memory leaks are notoriously hard to replicate, so I am not hopeful that Frederik can isolate the problem. Perhaps the particular errors in the screenshot will provide a clue. In any case, I am reporting the incident.
If anyone else sees any behavior like this, please report it.