This bug was reported at 9.2, but I don't have the NIM number. There's a noticeable memory leak when repeatedly rendering and querying data in ArcMap or ArcReader from a compressed file geodatabase. As a result, performance would deteriorate over time as available memory is consumed. The problem is not present with an uncompressed file geodatabase. Although this is not a critical bug for us in terms of workflow, it would save some time in copying basemap datasets to our field people if we could compress them. 😉
Actually, the amount of memory leaked at 9.4 beta 1 seems half that at 9.3.1, but it's still definitely there.
Thanks for reporting this, we would like to fix this further. Can you describe your data and what it is you are doing in ArcMap to see the memory leak? If you can describe the steps I need to take, I will attempt to reproduce it here with my own data.
I'm displaying a pretty good mix of features: polygons, lines, points, and annotation. Some features are labelled. I zoom to a scale where pretty much everything is displayed, say 1:2400, and start panning around with the task manager active, say 4-8 miles. If the file GDB is uncompressed, the memory consumption level stays pretty constant; but if the file GDB is compressed, I can watch the level climbing as previously unrendered features are rendered.
Thanks for your quick response. I tried to duplicate the conditions you described but I was unable to reproduce the problem. Can you please be more specific about your data and I will try again? Some details that will be helpful are:
How many features in your map? And if you can attach screenshots of your TOC and map please do How many feature classes? How dense are features, are there a lot of vertices? Any other data types you did not mention, ex. raster? How many seconds does it take to render for each pan?