+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 <jbarr...@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 <aba...@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 <u...@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. > >>> > > > >
