# Share my screen 2 times is not possible (Lost Sessions / Nodes)

**URL:** <https://openvidu.discourse.group/t/share-my-screen-2-times-is-not-possible-lost-sessions-nodes/516>\
**Category:** Issues developing apps\
**Tags:** v2\
**Created:** [April 21, 2020, 7:42am UTC](https://openvidu.discourse.group/t/share-my-screen-2-times-is-not-possible-lost-sessions-nodes/516 "2020-04-21T07:42:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![webgondel](https://avatars.discourse-cdn.com/v4/letter/w/7feea3/32.png) [@webgondel](https://openvidu.discourse.group/u/webgondel)\
**Post date:** [April 21, 2020, 7:42am UTC](https://openvidu.discourse.group/t/share-my-screen-2-times-is-not-possible-lost-sessions-nodes/516/1 "2020-04-21T07:42:06Z")

</div>

Hello everybody!

Our Plan is to release a huge school cloud / video software tool in the next couple of days / weeks.

We have the **OpenVidu Call** prodcut type running and we are trying the PRO Version at the moment. Everything was working very well, except the RE screensharing.

Means:

If I share my screen and quit this screensharing and after a while i want to share my screen again, all users in the video conference call only can see a grey monitor instead of my shared window…

I have also found out why (please have a look at this screenshot)

 ![Bildschirmfoto 2020-04-21 um 09.42.29](https://global.discourse-cdn.com/free1/uploads/openvidu/original/1X/7b0f0d1ffb831e268f97a265e6f03c475200bbf6.jpeg)

Everytime a user quitted the screen sharing in the graph is one new LOST node more to find. In my screenshot you can see for example the nodes

9  
10  
13  
8  
6  
7  
5

and

12

**The solution was:**

Go to the Deleting all nodes which are NOT connected with the innter acitve runnin users / nodes (lets call them “lost nodes” 🙂 )

But how can we avoid this problem or let the system delete this quitted screenSharing sessions automatically? Do we have to set something special?

Thx for your help and keep this GREAT project up please 🙂

bye

---

<div class="post-metadata">

**Author:** ![CSantosM](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/csantosm/32/16_2.png) [@CSantosM](https://openvidu.discourse.group/u/CSantosM)\
**Post date:** [April 21, 2020, 8:02am UTC](https://openvidu.discourse.group/t/share-my-screen-2-times-is-not-possible-lost-sessions-nodes/516/2 "2020-04-21T08:02:26Z")

</div>

Hello @webgondel,

Are you using OpenVidu Call 2.12.0? This version was a bug with screenshare.

We’re working on release the 2.13.0 version this week, meanwhile you can check the 2.13.0-beta5 using the [docker image](https://hub.docker.com/r/openvidu/openvidu-call/tags) or clone the master branch of [OpenVidu Call repository](https://github.com/OpenVidu/openvidu-call) with some bugs solved.

We’ll update the docs as soon as possible.

Regards

---

<div class="post-metadata">

**Author:** ![webgondel](https://avatars.discourse-cdn.com/v4/letter/w/7feea3/32.png) [@webgondel](https://openvidu.discourse.group/u/webgondel)\
**Post date:** [April 21, 2020, 8:46am UTC](https://openvidu.discourse.group/t/share-my-screen-2-times-is-not-possible-lost-sessions-nodes/516/3 "2020-04-21T08:46:56Z")

</div>

Hello @CSantosM

thx for your fast reply.

After you have released the new 2.13.0 \>\> How can we deploy on our AWS instances?  
Is there a specific pull process or do we just have to reInstall the AWS instance completly?

Thx for your help!

Thx

---

<div class="post-metadata">

**Author:** ![CSantosM](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/csantosm/32/16_2.png) [@CSantosM](https://openvidu.discourse.group/u/CSantosM)\
**Post date:** [April 21, 2020, 9:12am UTC](https://openvidu.discourse.group/t/share-my-screen-2-times-is-not-possible-lost-sessions-nodes/516/4 "2020-04-21T09:12:41Z")

</div>

Well, we’re working on a new docker-compose deployment so you will have to update the docker image.

It will be all documented in our next release.

Stay tuned