payload: {"action":"closed","issue":{"url":"https://api.github.com/repos/fabricjs/fabric.js/issues/5780","repository_url":"https://api.github.com/repos/fabricjs/fabric.js","labels_url":"https://api.github.com/repos/fabricjs/fabric.js/issues/5780/labels{/name}","comments_url":"https://api.github.com/repos/fabricjs/fabric.js/issues/5780/comments","events_url":"https://api.github.com/repos/fabricjs/fabric.js/issues/5780/events","html_url":"https://github.com/fabricjs/fabric.js/issues/5780","id":461174172,"node_id":"MDU6SXNzdWU0NjExNzQxNzI=","number":5780,"title":"Ipad: canvas memory use exceeds the maximum limit","user":{"login":"bassemBMI","id":657496,"node_id":"MDQ6VXNlcjY1NzQ5Ng==","avatar_url":"https://avatars1.githubusercontent.com/u/657496?v=4","gravatar_id":"","url":"https://api.github.com/users/bassemBMI","html_url":"https://github.com/bassemBMI","followers_url":"https://api.github.com/users/bassemBMI/followers","following_url":"https://api.github.com/users/bassemBMI/following{/other_user}","gists_url":"https://api.github.com/users/bassemBMI/gists{/gist_id}","starred_url":"https://api.github.com/users/bassemBMI/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bassemBMI/subscriptions","organizations_url":"https://api.github.com/users/bassemBMI/orgs","repos_url":"https://api.github.com/users/bassemBMI/repos","events_url":"https://api.github.com/users/bassemBMI/events{/privacy}","received_events_url":"https://api.github.com/users/bassemBMI/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2019-06-26T20:48:03Z","updated_at":"2019-06-27T20:38:32Z","closed_at":"2019-06-27T20:38:32Z","author_association":"NONE","body":"# Context:\r\n\r\nWhile implementing FabricJS, we have encountered a canvas memory limit error.\r\nWhile FabricJS alone is not the reason for the memory consumption(we have other components that use canvas too)\r\nwe have noticed that an older version of Fabric (1.3.0) merge all drawing in once canvas thus keeping canvas memory\r\nconsumption manageable\r\n\r\n\r\nTo illustrate our scenario please consider the following screenshots of safari devtoos -> canvas tab:\r\n\r\nLatest version:\r\n![image](https://user-images.githubusercontent.com/657496/60213543-ba6c7400-9831-11e9-86d8-00d633823cdb.png)\r\n\r\n1.3.0 version:\r\n![image](https://user-images.githubusercontent.com/657496/60213667-fe5f7900-9831-11e9-8f34-2697959e7e4b.png)\r\n\r\nWe can see that in the latest version, every action lives in a separate canvas while in the old version everything is merged in the main canvas\r\n\r\n# Question:\r\n\r\nIs there a way in the latest version of FabricJS to force all drawing and actions to apply only in the main canvas without creating secondary canvases\r\n\r\nPlease note that we have tried to deactivate the object cache without success:\r\n```\r\nfabric.Object.prototype.objectCaching = false;\r\n```\r\n\r\nhttp://fabricjs.com/fabric-object-caching\r\n\r\nThanks."}}
other: {"actor":{"display_login":"bassemBMI"}}