Ticket #163 (closed defect: fixed)
CapeRegistry wrappers leak memory
| Reported by: | jasper | Owned by: | jasper |
|---|---|---|---|
| Priority: | major | Milestone: | Maintenance of Phase II |
| Component: | Client Header Files | Version: | 1.2.0.11 |
| Keywords: | Cc: |
Description
The wrappers for CapeRegistryWriter? and CapeRegistryKeyReader? add a reference too many to the constructed object, causing their memory not to be released (memory leak).
Code that uses these types (CapeRegistryWriter? and CapeRegistryKeyReader?) directly should be rebuilt against the new client headers. Most code would not use these types directly (but would use the Registrar types instead)
Change History
comment:2 Changed 2 years ago by michelpons
With "Most code would not use these types directly (but would use the Registrar types instead)" are you speaking of COBIA-based applications like Multiflash and would they be impacted or not by this issue (now resolved) if using the Registrar types?
comment:3 follow-up: ↓ 4 Changed 2 years ago by jasper
I am not sure - the impact would in any case be small - some memory that remains allocated until the process exits.
comment:4 in reply to: ↑ 3 Changed 2 years ago by jasper
Replying to jasper:
I am not sure - the impact would in any case be small - some memory that remains allocated until the process exits.
I would think this would affect COBIA based PMEs mostly as they use the registry when running 'normally'. COBIA PMCs only use the registry when registering or unregistering themselves, typically during (un-)installation only.
In [ed9f2930d54978488ec3f28f62a1d8bb2fe46a4f]: