Kind of related to the old #1612 and #5840, anyone trying to be smart and adding properties to a pooled non-persisted event will cause those to properties to remain in the pool, causing a memory leak of sorts. Could it make sense to Object.seal(event) the events, that way we ensure that users can't mess with the event object in bad or unsupported ways.
Should probably do this instead: #5853 (comment)
Kind of related to the old #1612 and #5840, anyone trying to be smart and adding properties to a pooled non-persisted event will cause those to properties to remain in the pool, causing a memory leak of sorts. Could it make sense to
Object.seal(event)the events, that way we ensure that users can't mess with the event object in bad or unsupported ways.Should probably do this instead: #5853 (comment)