-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
loowid keeps crashing #202
Comments
Hi, I've been trying to reproduce the bug but I couldn't. How do you are entering or leaving? Are you using the "Leave room" button, or are doing another thing. Are you entering/leave with the room owner or a viewer? Thanks for helping us to improve LooWID. |
People simply close the browser and not use the leave room
…--
Vr, Frank
From: Alexandre Ballesté [mailto:notifications@github.com]
Sent: Friday, January 13, 2017 11:35 AM
To: loowid/loowid <loowid@noreply.github.com>
Cc: Frank Tucker <frank.tucker@microhealthllc.com>; Author <author@noreply.github.com>
Subject: Re: [loowid/loowid] loowid keeps crashing (#202)
Hi, I've been trying to reproduce the bug but I couldn't. How do you are entering or leaving? Are you using the "Leave room" button, or are doing another thing. Are you entering/leave with the room owner or a viewer?
Thanks for helping us to improve LooWID.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#202 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADgTo9bFvSciIjN4NIhcOey9vILd-1mVks5rR6e3gaJpZM4Lh0cy>.
|
oh btw, here is our implementation and customization. pretty much the standard loowid, just some customization on the landing page and theme. https://meet.microhealthllc.com/#!/ As mentioned...keep closing the browser and reopening...it will crash |
one more thing if you take a look, we implemented a dial in number by clicking the information button. easiest way for us to mod the software without changing the code where we couldn't get updates upstream from source code |
I hope I'll find time to try to solve the issue this weekend.
El jue., 19 ene. 2017 0:08, bluenevus <notifications@github.com> escribió:
… one more thing if you take a look, we implemented a dial in number by
clicking the information button. easiest way for us to mod the software
without changing the code where we couldn't get updates upstream from
source code
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#202 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABqiHadHdwvjZmsof0VgXCWe-5LzgT00ks5rTptZgaJpZM4Lh0cy>
.
|
Wow, you're not going to believe that, but I'm not able to reproduce that... I've tried in local and also in www.loowid.com. I've tried to exit as moderator and viewer 7 or 8 times just closing the browser tab and nothing broke. :-( I've you can provide the exact steps to reproduce the case or just record a short video it would be very useful for us to solve this problem. We really appreciate your work here. |
if someone enters, leaves, enters, leaves the conference loowid crashes.
I have to kill mongod then kill loowid then restart both to get it back up.
The text was updated successfully, but these errors were encountered: