orbiter.dispose call generated error message

10 views
Skip to first unread message

Toby

unread,
Apr 23, 2019, 6:23:42 PM4/23/19
to Union Platform
For reasons not relevant here, I added an "orbiter.dispose()" call to some testing code.
This produces an error message in the browser log (see below).

Here is a minimal test page which will demonstrate the problem.

<script type="text/javascript" src="../orbiter/Orb_2_1_min.js"> </script>
<script type="text/javascript">
var orbiter = null;
  orbiter
= new net.user1.orbiter.Orbiter();
  orbiter
.dispose();
</script>

 Then the following appears in the browser's console log (the important part is at the end: ( TypeError: this.msgManager is not a function )
My guess on that is that within the orbiter code, it is making a call to msgManager after having already disposed of it.

INFO: User Agent: Mozilla/5.0 (Windows NT 6.0; rv:52.0) Gecko/20100101 Firefox
INFO: Union Client Version: Orbiter 2.1.1 (Build 856)
INFO: Client UPC Protocol Version: 1.10.3
INFO: [CONNECTION_MANAGER] Ready timeout set to 10000 ms.
INFO: [CONNECTION_MANAGER] Global server affinity selected. Using current environment's shared server affinity.
INFO: [CONNECTION_MONITOR] Assigning auto-reconnect frequency settings: [minMS: -1, maxMS: -1, delayFirstAttempt: false].
INFO: [CONNECTION_MONITOR] Auto-reconnect attempt limit set to none.
INFO: [CONNECTION_MONITOR] Connection timeout set to 60000 ms.
INFO: [CONNECTION_MONITOR] Heartbeat frequency set to 10000 ms.
INFO:  [ORBITER] Initialization complete.
INFO:  [ORBITER] Beginning disposal of all resources...
INFO:  [CONNECTION_MANAGER] removeAllConnections() ignored.  No connections to remove
.
INFO:  [ROOM_MANAGER] Disposing resources.
TypeError: this.msgManager is not a function[Learn More]

Reply all
Reply to author
Forward
0 new messages