Memory Leak #1

New Issue

EpicKnarvik97 · 2023-03-18T16:25:57+01:00

EpicKnarvik97 commented

2023-03-18 16:25:57 +01:00

A memory leak has been detected related to the storage of signs. For some unknown reason, the ConfigManager used to store sign ends up with a YamlConfiguration which constructs millions of objects. This might be related to the fact that signs are loaded from file once every second.

In addition to fixing the leak if an obvious problematic line is found, changes must be made to only save and load files when necessary to reduce overhead.

While the problem is definitely in fileC's YamlConfiguration's YamlConstructor's constructed objects, I'm not entirely sure why that ends up with over 8000000 objects after 24 hours.

A memory leak has been detected related to the storage of signs. For some unknown reason, the ConfigManager used to store sign ends up with a YamlConfiguration which constructs millions of objects. This might be related to the fact that signs are loaded from file once every second. In addition to fixing the leak if an obvious problematic line is found, changes must be made to only save and load files when necessary to reduce overhead. While the problem is definitely in fileC's YamlConfiguration's YamlConstructor's constructed objects, I'm not entirely sure why that ends up with over 8000000 objects after 24 hours.

EpicKnarvik97 added the

bug

label 2023-03-18 16:25:57 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: EpicKnarvik97/BlockHunt#1