67fca54d76
Scenario: presenter`s client could crash when the presenter changed while they were sharing their screen That is due to a race condition on the stop procedure in the bridge: two stops can be triggered (one from the server-side websocket tear off and another from the client itself detecting the presenter change) That could create a scenario where the broker was cleaned in one stop procedure after the second had checked its availability, causing an attribute access of a null member |
||
|---|---|---|
| .. | ||
| .meteor | ||
| client | ||
| dev_local_deployment | ||
| imports | ||
| private | ||
| public | ||
| server | ||
| tests | ||
| .dockerignore | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitignore | ||
| deploy_to_usr_share.sh | ||
| docker-entrypoint.sh | ||
| Dockerfile | ||
| Dockerfile.dev | ||
| package-lock.json | ||
| package.json | ||
| test-html5.sh | ||
| TRANSIFEX_PULL_INSTRUCTIONS.md | ||
| transifex.sh | ||