[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Memory leak in OpenEdge.Net.HTTP classes?

  • Thread starter Thread starter Peter Judge
  • Start date Start date
Status
Not open for further replies.
P

Peter Judge

Guest
David, This is expected behaviour – the HTTP client (and other components) use a registry of character/names + types (instance of Progress.Lang.Class) for a bunch of stuff . There are around 110 registry entries in the OpenEdge.Net.pl library and about 15 in the OpenEdge.Core.pl. Each time you do a GET-CLASS() or equivalent, a new instance of that class is created. These are, to the best of my understanding, static in the AVM (per session). I would expect a certain number of objects to be created in the various builder registries and then for the agents’ memory consumption to plateau. You’re looking at the stacks in OEE by the looks of things. If you use the ABL Objects report you get the same information but more of it. You can also make these calls from an OpenAPI doc that ‘s in 11.7.4. To set it up check out documentation.progress.com/.../index.html . You’ll need to get the agents, and then enable ABLObjects. Then run your stuff and then GetABLObjects. This has the benefit of containing the OOABL type name. You can remove your types and see what’s left (keep Progress.* and OpenEdge.* references), and if that grows then there’s definitely a leak on our side.

Continue reading...
 
Status
Not open for further replies.
Back
Top