I posted a build 381:
https://forums.homeseer.com/showthread.php?t=181241
Anyone is welcome to try it, but I am most interested in users who have seen the plugin event queue fill rapidly.
This build adds a queue and thread per plugin for handling event callbacks. Event callbacks are things like device changes, event log entries, and such. It appears that some or one plugin is not returning from this call and that allows the queue to fill and use memory. It will also cause plugins to not operate properly.
Each plugin now has its own queue with a max size of 50 entries. If a plugin stops responding HS will log a message with the plugin name so we can see which one it is. But with a max queue size memory will not rise. Other plugins will continue to operate normally.
https://forums.homeseer.com/showthread.php?t=181241
Anyone is welcome to try it, but I am most interested in users who have seen the plugin event queue fill rapidly.
This build adds a queue and thread per plugin for handling event callbacks. Event callbacks are things like device changes, event log entries, and such. It appears that some or one plugin is not returning from this call and that allows the queue to fill and use memory. It will also cause plugins to not operate properly.
Each plugin now has its own queue with a max size of 50 entries. If a plugin stops responding HS will log a message with the plugin name so we can see which one it is. But with a max queue size memory will not rise. Other plugins will continue to operate normally.
Comment