{"action":"created","issue":{"url":"https://api.github.com/repos/4ian/GDevelop/issues/728","repository_url":"https://api.github.com/repos/4ian/GDevelop","labels_url":"https://api.github.com/repos/4ian/GDevelop/issues/728/labels{/name}","comments_url":"https://api.github.com/repos/4ian/GDevelop/issues/728/comments","events_url":"https://api.github.com/repos/4ian/GDevelop/issues/728/events","html_url":"https://github.com/4ian/GDevelop/issues/728","id":377305436,"node_id":"MDU6SXNzdWUzNzczMDU0MzY=","number":728,"title":"Memory consumption constantly rising with scene editor open","user":{"login":"Wend1go","id":7413059,"node_id":"MDQ6VXNlcjc0MTMwNTk=","avatar_url":"https://avatars0.githubusercontent.com/u/7413059?v=4","gravatar_id":"","url":"https://api.github.com/users/Wend1go","html_url":"https://github.com/Wend1go","followers_url":"https://api.github.com/users/Wend1go/followers","following_url":"https://api.github.com/users/Wend1go/following{/other_user}","gists_url":"https://api.github.com/users/Wend1go/gists{/gist_id}","starred_url":"https://api.github.com/users/Wend1go/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Wend1go/subscriptions","organizations_url":"https://api.github.com/users/Wend1go/orgs","repos_url":"https://api.github.com/users/Wend1go/repos","events_url":"https://api.github.com/users/Wend1go/events{/privacy}","received_events_url":"https://api.github.com/users/Wend1go/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-11-05T09:02:04Z","updated_at":"2018-11-06T11:12:37Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"## Describe the bug\r\nThe memory consumption of GD5 Beta 50 and newer versions (Beta 48 and lower are not affected) rises by about 1% point per second when the scene editor is open on my test VM.\r\nAfter a while actions like dragging the view or selecting an instance become sluggish and get performed after a delay of several seconds until the IDE stops responding and has to be killed.\r\nThe events editor seems to be not affected by this. If you manage to activate the events tab before it stops responding the memory rapidly drops to the usual level of around 6% and working with events is smooth as normal.\r\nThis happens on a VM with a Linux Mint 18.3 / 64 Bit / 4GB RAM. But might also happen on low spec PCs.\r\n\r\n## To Reproduce\r\n1) Start GD5 IDE (Beta 50 or newer)\r\n2) Open a test game\r\n3) Open a scene\r\n4) Leave it running for some time -> Memory consumption rises about 1% point each second\r\n\r\n* Testgame:\r\n[dungeon.tar.gz](https://github.com/4ian/GDevelop/files/2547501/dungeon.tar.gz)\r\nThis test game is nothing fancy, just 10x10 sprite objects.\r\n\r\n## Other details\r\nThe issue is **not** present on my main developing machine (also Linux Mint 18.3). Looks like it only affects machines with crappy hardware. The bug was introduced with Beta50, the test game runs smoothly in older versions of GD5 in the same VM.\r\n\r\nGD5 Beta 48:\r\n![gd48_dungeon](https://user-images.githubusercontent.com/7413059/48001773-d76cff00-e109-11e8-8b10-deef2cbf8a79.png)\r\nLooks ok\r\n\r\nGD5 Beta 55:\r\n![gd55_dungeon](https://user-images.githubusercontent.com/7413059/48001778-da67ef80-e109-11e8-8be4-b89870ea6844.png)\r\nThe red markings are all \"animation frame fired (raven.js: 1086 recurring handler took (60-100ms))\r\n (unfortunately I can't upload a report since even 10sec of profiling is around 100MB in size)\r\n\r\nEDIT:\r\nSo raven.js is for error tracking. The VM doesn't have internet access. Maybe it is constantly stacking reports in memory that the script is unable to send."},"comment":{"url":"https://api.github.com/repos/4ian/GDevelop/issues/comments/436217227","html_url":"https://github.com/4ian/GDevelop/issues/728#issuecomment-436217227","issue_url":"https://api.github.com/repos/4ian/GDevelop/issues/728","id":436217227,"node_id":"MDEyOklzc3VlQ29tbWVudDQzNjIxNzIyNw==","user":{"login":"Wend1go","id":7413059,"node_id":"MDQ6VXNlcjc0MTMwNTk=","avatar_url":"https://avatars0.githubusercontent.com/u/7413059?v=4","gravatar_id":"","url":"https://api.github.com/users/Wend1go","html_url":"https://github.com/Wend1go","followers_url":"https://api.github.com/users/Wend1go/followers","following_url":"https://api.github.com/users/Wend1go/following{/other_user}","gists_url":"https://api.github.com/users/Wend1go/gists{/gist_id}","starred_url":"https://api.github.com/users/Wend1go/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Wend1go/subscriptions","organizations_url":"https://api.github.com/users/Wend1go/orgs","repos_url":"https://api.github.com/users/Wend1go/repos","events_url":"https://api.github.com/users/Wend1go/events{/privacy}","received_events_url":"https://api.github.com/users/Wend1go/received_events","type":"User","site_admin":false},"created_at":"2018-11-06T11:12:37Z","updated_at":"2018-11-06T11:12:37Z","author_association":"CONTRIBUTOR","body":"The performance has never been great since the Virtual Box driver can only achieve OpenGL 2.1 via software rendering, hence the high CPU load. But it was still enough to work on my projects.\r\n\r\nI installed a new VM with Manjaro (all updates installed, newest kernel and up to date guest additions) and I get the same result as with the old Mint18.3 VM.\r\n\r\nHere are the profile files (Zipping the files did wonders with the size):\r\n[Profile-LM18.3.json.tar.gz](https://github.com/4ian/GDevelop/files/2552873/Profile-LM18.3.json.tar.gz)\r\n[Profile-Manjaro17.json.tar.gz](https://github.com/4ian/GDevelop/files/2552874/Profile-Manjaro17.json.tar.gz)\r\n"}}
{"actor":{"display_login":"Wend1go"}}