{"push_id":1150775356,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"5375fc5c3c9001f988bb3e40c77f82c84f519b71","before":"890ccefed083b7176b6970a19dc27459ccb8fc2d","commits":[{"sha":"eaf12da29e9bd185ae66495eb6328cc310767aa4","author":{"name":"Derrell Lipman","email":"34eb4c4c8e8a58abcd238d75cbe917496664f3f7@unwireduniverse.com"},"message":"Fixes memory leak in qx.event.message.Bus\n\nIt is the responsibility of the dude who instantiates an object to ensure that\nthe object is disposed. The method dispatchByName was instantiating a\nqx.event.message.Message object and setting its 'data' property. That data can\nbe large, and that property data does not get freed (by Chrome 50 nor 52) when\nthe object goes out of scope.\n\nThis commit ensures that the object is properly disposed.\n\n(Note that when the dispatch() method is called directly from outside of\nqooxdoo, it is the caller's responsibility to free the message that she has\ninstantiated and passed in. Only in the case of dispatchByName is the Message\nobject instantiated internally, and thus must be disposed internally.)\n\nDerrell","distinct":true,"url":"https://api.github.com/repos/qooxdoo/qooxdoo/commits/eaf12da29e9bd185ae66495eb6328cc310767aa4"},{"sha":"5375fc5c3c9001f988bb3e40c77f82c84f519b71","author":{"name":"Tobias Oetiker","email":"f3d320b7ede34dc182b205e5417108eecd3f29b0@oetiker.ch"},"message":"Merge pull request #9038 from derrell/message-bus-mem-leak\n\nFixes memory leak in qx.event.message.Bus","distinct":true,"url":"https://api.github.com/repos/qooxdoo/qooxdoo/commits/5375fc5c3c9001f988bb3e40c77f82c84f519b71"}]}
{"actor":{"display_login":"oetiker"}}