Every time a window is closed or its URL is changed it fires an "unload" event that the contained bridge instances use to remove the cookie based marker that informs all bridge instances about the state of blocking connection (on/off). In Opera the "unload" (received through a handler set on "document.onunload" property) event is not fired because Opera chose to freeze and persist the state of the interpreter and document for caching purposes. As a side effect, when the window that contains the bridge instance owning the blocking connection is closed the rest of the bridge instances are not aware that a new blocking connection needs to be created since the cookie marker was never removed (which is the equivalent to the "off" state).

One solution would be to implement some sort of leasing mechanism for the window owning the blocking connection, lease that would be renewed periodically until the window is closed.

As far as I understand, dispose-views request is also not send due to this behaviour of Opera, so there is no way to free resources when the window is closed.

Need to review latest Opera release (9.5, 9.5.2) to see if they've made any changes in this area.

Need to investigate a resolution for this.

Implement lease mechanism for blocking connection.