You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The OPM module hasn't seen any serious contribution for many years. This is due to the fact, that the person who built it, no longer is active in the project.
As far as I know, there isn't anyone else really deeply involved in this. I think I was the only one occasionally working on it.
However have I stopped contributing to the project for free ... I would be willing to have a look at this and your other issue, for a donation of at least 60€ to my BuyMeACoffee page https://buymeacoffee.com/christoferu
What happened?
Production use case:
Issue:
Comparing dumps (from production) show an increase of byte[] objects like:
java.lang.String#45053 : FooRxEntity$ByteBuddy$opFq0T9M$auxiliary$5LGzfXOE
.The ByteBuddy instances are created here:
org.apache.plc4x.java.opm.PlcEntityManager#connect(java.lang.Class<T>, java.lang.String, T)
therefore I think that PlcEntityManager is responsible for the leak.
Code to reproduce the issue:
And the entity:
The test is started with VM options
-Xms128m -Xmx128m
. After ~4 minutes OOM is thrown.I can reproduce the OOE with a real connection. This take a lot more time because the plc support a max reading rate of ~300ms.
Real test:
Mock dump:
heapdump-1733998935197.zip
Production dump:
heapdump-1732691913936.zip
Please let me know if you need more details and thank you in advance.
Version
v0.12.0
Programming Languages
Protocols
The text was updated successfully, but these errors were encountered: