14651 2011-11-01 09:19:34 +0000 i think the websocket garbage collection rules might need tweaking now that message can't be fired in CLOSING (can error be fired in CLOSING?) 2012-07-18 18:48:29 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#garbage-collection-2 P3 normal Unsorted 1 contributor ian ian mike zcorpan contributor oldest_to_newest 59382 0 contributor 2011-11-01 09:19:34 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/network.html Multipage: http://www.whatwg.org/C#garbage-collection-2 Complete: http://www.whatwg.org/c#garbage-collection-2 Comment: i think the websocket garbage collection rules might need tweaking now that message can't be fired in CLOSING (can error be fired in CLOSING?) Posted from: 88.131.66.80 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.15 Safari/535.7 59397 1 ian 2011-11-01 15:40:33 +0000 Can you elaborate? 59402 2 zcorpan 2011-11-01 15:44:05 +0000 The GC rules assume that 'message' events can be fired when readyState is CLOSING, so makes sure not to GC if there are listeners for 'message'. But since we now don't fire 'message' in CLOSING, we can allow the object to be GCed. 59406 3 ian 2011-11-01 16:13:14 +0000 Oh, WebSocket. Sorry, I thought we were talking about EventSource. 59407 4 contributor 2011-11-01 16:13:29 +0000 Checked in as WHATWG revision r6805. Check-in comment: Allow a WebSocket object with only a message handler to be GC'ed once it gets to CLOSING. http://html5.org/tools/web-apps-tracker?from=6804&to=6805