On Wed, 10 Dec 2025 05:33:02 GMT, Sergey Bylokhov <[email protected]> wrote:
> > Probably we should remove this listener when we enter serialization for > > editing JTable but it seems it throws exception before calling > > JTable.writeObject so we cannot remove the listener there..so I think > > present fix is good enough to make it not serialized.. > > You made the field of that object non-serializable, but the GenericEditor > object itself is still serializable. After deserialization, we end up with a > leaked GenericEditor instance whose "constructor" field is null. If we > serialize the object multiple times, we may end up with multiple > GenericEditor instances. ok..you are telling the problem but there is no discernible solution to it..we need to remove the editor only during serialization but writeObject is not getting called..any solution you have in mind.. ------------- PR Comment: https://git.openjdk.org/jdk/pull/28627#issuecomment-3635474599
