geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lynn Hughes-Godfrey <lhughesgodf...@pivotal.io>
Subject Re: GEODE-6662 for 1.9.0
Date Wed, 17 Apr 2019 20:22:47 GMT
+1 to Bruce & Anthony's suggestion to fix it.  GemFire servers are meant to
be long running processes.

On Wed, Apr 17, 2019 at 12:09 PM Jacob Barrett <jbarrett@pivotal.io> wrote:

> If it Leakes on object overt the life of the application, no biggy. If it
> leaks an object frequently, say every time you call get, then fixxy.
>
> -Jake
>
> > On Apr 17, 2019, at 12:05 PM, Anthony Baker <abaker@pivotal.io> wrote:
> >
> > If a geode process leaks memory, I think that’s a critical issue.
> >
> > Anthony
> >
> >
> >> On Apr 17, 2019, at 11:45 AM, Udo Kohlmeyer <udo@apache.org> wrote:
> >>
> >> Unless this is a critical issue I'd vote -1 for including this.
> >>
> >> The process to release 1.9 has already been started and should be
> closed to anything other than critical CVE's.
> >>
> >> --Udo
> >>
> >> On 4/17/19 11:30, Bruce Schuchardt wrote:
> >>> I'd like to include the fix for this memory leak that Darrel found.
> It's new in 1.9 and the fix is pretty simple - I'm putting up a PR now.
> >>>
> >
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message