{"action":"created","issue":{"url":"https://api.github.com/repos/ioBroker/ioBroker.mqtt/issues/47","repository_url":"https://api.github.com/repos/ioBroker/ioBroker.mqtt","labels_url":"https://api.github.com/repos/ioBroker/ioBroker.mqtt/issues/47/labels{/name}","comments_url":"https://api.github.com/repos/ioBroker/ioBroker.mqtt/issues/47/comments","events_url":"https://api.github.com/repos/ioBroker/ioBroker.mqtt/issues/47/events","html_url":"https://github.com/ioBroker/ioBroker.mqtt/issues/47","id":424894982,"node_id":"MDU6SXNzdWU0MjQ4OTQ5ODI=","number":47,"title":"MQTT uses up all memory","user":{"login":"mediaDS","id":48488629,"node_id":"MDQ6VXNlcjQ4NDg4NjI5","avatar_url":"https://avatars1.githubusercontent.com/u/48488629?v=4","gravatar_id":"","url":"https://api.github.com/users/mediaDS","html_url":"https://github.com/mediaDS","followers_url":"https://api.github.com/users/mediaDS/followers","following_url":"https://api.github.com/users/mediaDS/following{/other_user}","gists_url":"https://api.github.com/users/mediaDS/gists{/gist_id}","starred_url":"https://api.github.com/users/mediaDS/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mediaDS/subscriptions","organizations_url":"https://api.github.com/users/mediaDS/orgs","repos_url":"https://api.github.com/users/mediaDS/repos","events_url":"https://api.github.com/users/mediaDS/events{/privacy}","received_events_url":"https://api.github.com/users/mediaDS/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":16,"created_at":"2019-03-25T13:14:02Z","updated_at":"2019-04-05T19:10:45Z","closed_at":"2019-04-05T07:14:48Z","author_association":"NONE","body":"ioBroker Admin 3.6.0\r\njs-Controller 1.4.2\r\nMQTT Broker 2.0.4\r\n\r\nioBroker runs on a Odroid C2 with 2GB RAM. There are three MQTT clients who send their telemetry to the broker, 2 ESP8266 with MQTT client and 1 Raspberry Pi 3B+ with Mosquitto.\r\n\r\nAfter a few hours the broker sucks up all memory - it grows from around 35.5MB after restart to about 920MB. I have to restart the adapter to get back to 35.5MB. Is this normal behauviour or a memory leak/bug?\r\n\r\nEdit:\r\n\r\nThe data packets from each client are between 20-200 bytes long and are send every 120 seconds.\r\n"},"comment":{"url":"https://api.github.com/repos/ioBroker/ioBroker.mqtt/issues/comments/480390319","html_url":"https://github.com/ioBroker/ioBroker.mqtt/issues/47#issuecomment-480390319","issue_url":"https://api.github.com/repos/ioBroker/ioBroker.mqtt/issues/47","id":480390319,"node_id":"MDEyOklzc3VlQ29tbWVudDQ4MDM5MDMxOQ==","user":{"login":"mediaDS","id":48488629,"node_id":"MDQ6VXNlcjQ4NDg4NjI5","avatar_url":"https://avatars1.githubusercontent.com/u/48488629?v=4","gravatar_id":"","url":"https://api.github.com/users/mediaDS","html_url":"https://github.com/mediaDS","followers_url":"https://api.github.com/users/mediaDS/followers","following_url":"https://api.github.com/users/mediaDS/following{/other_user}","gists_url":"https://api.github.com/users/mediaDS/gists{/gist_id}","starred_url":"https://api.github.com/users/mediaDS/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mediaDS/subscriptions","organizations_url":"https://api.github.com/users/mediaDS/orgs","repos_url":"https://api.github.com/users/mediaDS/repos","events_url":"https://api.github.com/users/mediaDS/events{/privacy}","received_events_url":"https://api.github.com/users/mediaDS/received_events","type":"User","site_admin":false},"created_at":"2019-04-05T19:10:45Z","updated_at":"2019-04-05T19:10:45Z","author_association":"NONE","body":"This is weird, everything is working now and the memory footprint stays stable at 99MB. I did not change anything. \r\nI think we can close this now - your adpater seems to work as it should. I will keep an eye on it over the next days. If there is any change I will let you know. \r\n\r\nKeep up the good work and have a nice weekend,\r\nDieter\r\n"}}
{"actor":{"display_login":"mediaDS"}}