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
Luos engine 2.X.X, but this bug still occurs on version 3.
Description of the bug
The Gate service is one of the only packages using the polling methodology to retrieve messages. The gate manages the messages service by service. If a service is excluded it will no longer be managed by the Gate. So if The Gate excludes some services due to temporary no response, if those services continue to send data to the Gate, messages will stack and overflow the RAM.
Possible solutions
Accepting messages from zombie services/nodes or non-referenced services/nodes is a security issue. It is very difficult to fix it on version 2.X.X, so this needs to be fixed on version 3.0.0.
The text was updated successfully, but these errors were encountered:
To fix this I had to add a condition on the reception filters. This operation may be done in IRQ (depending on the network), but we have no other choice.
Thanks to this we now have good behavior.
Which version the bug has been detected on
Luos engine 2.X.X, but this bug still occurs on version 3.
Description of the bug
The Gate service is one of the only packages using the polling methodology to retrieve messages. The gate manages the messages service by service. If a service is excluded it will no longer be managed by the Gate. So if The Gate excludes some services due to temporary no response, if those services continue to send data to the Gate, messages will stack and overflow the RAM.
Possible solutions
Accepting messages from zombie services/nodes or non-referenced services/nodes is a security issue. It is very difficult to fix it on version 2.X.X, so this needs to be fixed on version 3.0.0.
The text was updated successfully, but these errors were encountered: