Icon View Incident Report

Serious Serious
Reported By: Jan-Erik Johansen
Reported On: 4/23/2009
For: Version 2.02 Build 11
# 3074 ElevateDB Sessions Not Releasing Memory for Cached Updates Manager Until Engine Shutdown

A few days ago I upgraded one webserver running 2.2.8 to 2.2.11 and it resulted in some strange memory issues.

Running 2.2.8 the edbserver runs with a memory useage of 40-80MB, however, the switch to 2.2.11 made the memory useage go sky-high. Memory consumption climbs steadily until it reaches 2GB and the performance is not in the same league as 2.2.8.

This, somehow, also turns the wp3 service into a memory hog.

Well, long story short, I switched back to 2.2.8 last night and performance is back to normal. (actually it is lightning fast, running on Intel X25-E SSD)

Comments Comments
The problem was with the introduction of cached updates internally in the engine. The cached updates manager was creating some in-memory files for internal usage and not deleting them when the session was disconnected. They would stay around until the engine (in this case the server) shut down.

Resolution Resolution
Fixed Problem on 9/30/2009 in version 2.03 build 4

Products Affected Products Affected
ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial