How to resolve FELIX-6591?

[Chris Rankin <ra...@gmail.com>]

Hi,

Can anyone help to progress https://issues.apache.org/jira/browse/FELIX-6591
please? This memory leak is causing us a certain amount of grief, and
although we have already identified a fix (as described in FELIX-6591),
we'd like to avoid creating our own version of `felix-security` if at all
possible.

Thanks,
Chris

Re: How to resolve FELIX-6591?

[Karl Pauls <ka...@gmail.com>]

Thanks a lot for the pr - I tested it a bit and it looks good. I applied
the PR to main now and will cut a new release of framework.security next
week.

Again, sorry for the delay.

regards,

Karl

On Thu, Apr 13, 2023 at 11:01 PM Karl Pauls <ka...@gmail.com> wrote:

> I'll try to have a look at it tomorrow - sorry for the delay.
>
> regards,
>
> Karl
>
> On Wed, Apr 12, 2023 at 6:16 PM Chris Rankin <ra...@gmail.com> wrote:
>
>> Hi,
>>
>> Can anyone help to progress
>> https://issues.apache.org/jira/browse/FELIX-6591
>> please? This memory leak is causing us a certain amount of grief, and
>> although we have already identified a fix (as described in FELIX-6591),
>> we'd like to avoid creating our own version of `felix-security` if at all
>> possible.
>>
>> Thanks,
>> Chris
>>
>
>
> --
> Karl Pauls
> karlpauls@gmail.com
>


-- 
Karl Pauls
karlpauls@gmail.com

Re: How to resolve FELIX-6591?

[Karl Pauls <ka...@gmail.com>]

I'll try to have a look at it tomorrow - sorry for the delay.

regards,

Karl

On Wed, Apr 12, 2023 at 6:16 PM Chris Rankin <ra...@gmail.com> wrote:

> Hi,
>
> Can anyone help to progress
> https://issues.apache.org/jira/browse/FELIX-6591
> please? This memory leak is causing us a certain amount of grief, and
> although we have already identified a fix (as described in FELIX-6591),
> we'd like to avoid creating our own version of `felix-security` if at all
> possible.
>
> Thanks,
> Chris
>


-- 
Karl Pauls
karlpauls@gmail.com