FYI regarding sage2 screen sharing

[Mike Freemon <mfreemon@xxxxxxxxxxxx>]

FYI for those doing screen sharing on the sage2 system:

Just share one screen per web UI instance.  See below for details.

I have confirmed that this does avoid the screen freeze/server crash 
problem.

- Mike


-------- Forwarded Message --------
Subject: 	Re: server crash while sharing multiple screens concurrently
from the same client
Date: 	Sun, 21 Jun 2015 20:26:06 -0700
From: 	Luc Renambot <renambot@xxxxxxxxx>
To: 	sage2@xxxxxxxxxxxxxxxx, mfreemon.nds@xxxxxxxxx

You can only share one content (screen or window) per Web UI, for now.
The trick to share multiple windows is to open multiple Web UI (in
multiple tabs for instance) and share one window within each tab.

Sorry for the inconvenience.

Luc


On Saturday, June 20, 2015 at 2:11:06 PM UTC-5, Mike Freemon wrote:

    Is sharing multiple screens concurrently from the same client 
supported?

    When I share two screens (not the entire screen), I see them stacked
    vertically and stuck together on the sage display.  If I stop
    sharing on one, the graphics show only a single title bar, which is
    frozen, while the other screen continues to work.  This condition
    frequently results in a server crash, with this message:

    /sage2/src/node-interactable.js:279

    results.push(this.layers[layerId].objects.search([point.x, point.y,
    point.x,
                        ^
    TypeError: Cannot read property 'objects' of undefined
         at InteractableManager.searchGeometry
    (/sage2/src/node-interactable.js:279:36)
         at SAGE2ItemList.findButtonByPoint
    (/sage2/src/node-sage2itemlist.js:113:27)
         at pointerMoveOnApplication (/sage2/server.js:4343:36)
         at updatePointerPosition (/sage2/server.js:4300:5)
         at pointerPosition (/sage2/server.js:4187:2)
         at Object.wsPointerPosition [as pointerPosition]
    (/sage2/server.js:742:2)
         at WebSocket.<anonymous> (/sage2/src/node-websocket.io.js:80:26)
         at WebSocket.emit (events.js:110:17)
         at Receiver.ontext 
(/sage2/node_modules/ws/lib/WebSocket.js:797:10)
         at /sage2/node_modules/ws/lib/Receiver.js:473:18

    I suspect that I can always reproduce the server crash if I knew
    exactly the sequence of clicks or cursor movements to perform.

    This occurs with multiple client O/Ss (Fedora 21, Win7) running
    google chrome v43 with the sage2 extension.

    The server is running inside docker.

    REPOSITORY          TAG                 IMAGE ID
    CREATED             VIRTUAL SIZE
    mvictoras/sage2     latest              0b0f2ce9c3ee        9 days
    ago          2.178 GB

    SAGE2>          Node Version: 12 (v0.12.4)
    SAGE2>          Detected Server OS as:  Linux
    SAGE2>          SAGE2 Short Version:    0.3.0
    ...
    SAGE2>          Full

Version:{base:"0.3.0",branch:"master",commit:"d469755",date:"2015/06/10"}

    Thank you.

    - Mike

--
You received this message because you are subscribed to the Google
Groups "SAGE2" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to sage2+unsubscribe@xxxxxxxxxxxxxxxx
<mailto:sage2+unsubscribe@xxxxxxxxxxxxxxxx>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage2/cf59b16a-4673-43a0-91e8-0c36cbcc96aa%40googlegroups.com 

<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_sage2_cf59b16a-2D4673-2D43a0-2D91e8-2D0c36cbcc96aa-2540googlegroups.com-3Futm-5Fmedium-3Demail-26utm-5Fsource-3Dfooter&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=iEj4zY2m23d9QPzTewICNOX29P1IYSX9q3kyeqIQKeo&m=twj9Vo72ulL5K8zGBDcU3SJkMVe9wmUQvB52dnWLQdw&s=oajSmu0s4hiuIv0-coJL5FBPmcv9goCwF4Cu5aTNPDw&e=>.
For more options, visit https://groups.google.com/d/optout
<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=iEj4zY2m23d9QPzTewICNOX29P1IYSX9q3kyeqIQKeo&m=twj9Vo72ulL5K8zGBDcU3SJkMVe9wmUQvB52dnWLQdw&s=7wR6p1rybFnI3v71zjRGiiUaXL2NOTEitT82PO60VRw&e=>.