Open sojharo opened 8 years ago
@sojharo You should look into browser - it sounds like we have some background work load running in browser
It seems the browser issue to me as well. When all the tabs are loading for first time. It does audio choppy issues. I think at the time being, sumaira, zarmeen and you are able to hear each other clearly.
I just tested the screen sharing on two person. It worked and nothing was proved to be wrong. At this time, all the tabs are done loading and there is nothing which is getting processed in the background.
I am looking into cpu profile now to see if i can find something there.
One day we should use another tool like Uber conference and see how quality.
Is your machine Linux or Windows?
It is linux and browser is chrome. the processor is AMD A6.
Let us use this tomorrow meeting. I would come as the same way with all tabs as I did today.
I am not sure it is your tab. I think it is more like some javascript running in the background.
Some of the angularjs watchers and foreach loopers also take cpu time according to following profile. I am not sure if this is normal for angularjs elements to take this time.
I think you are on to some thing :-)
Appear.in CPU profile showed less cpu consumption. They use jquery.
I think the issue is some change in our logic. We did not have this issue before.
I have gone through the code and could not find any change which might affect the performance. Let's test one more time in today's meeting with interns. I would come from my own laptop to see if it is browser issue. The first time loading of browser does lot of processing to open lots of tabs. I would close other tabs to see if it works or not.
Going to use the same issue for audio quality problems that we had. Sumaira's voice got cut off for sir and only I was able to hear her. She was only able to hear me.
@sojharo
I think we need to attack this into multiple fronts. So far we have gone into a crisis mode and when the issue goes away we forget about it.
We can be having this issue for multiple reasons:
Today's issue was that the voice was very choppy.
I think we ned to build or use some tools to know more about these issues.
Can we build a tool to look at backend by calling our API or otherwise to see when session got started or dropped? So every time we have an issue we run basic diagnostic to get the information.
Can we run a tool on a daily basis to see all the failures on our server side? I do not think we ned to write it. There are lots of tools out there that we can use to look at logs.
If we think, the issue is on the client side what tooling we would need.
What I am asking you is to sit back and think through it and see how do we approach these problems.
I am not proposing we build lots of tools but at least analyze how to approach this whole issue.
Give some thought and let's discuss this.
@sojharo ???
why no update for the last 4 days?
I need to do testing and debugging on this with interns as I was unable to properly debug it on one computer. Interns has working day on Wednesday.
However, I had looked into logs too. One problem that I found is that sometimes during the running conference camera and mic are released. Browser no more captures them. Then we have to refresh it. There is no obvious error shown on why browser releases the camera. This happened on my ubuntu. Not sure about other operating systems. I will test it with interns.
I have worked more on it and added logs in the changes made by zarmeen too. After this, did some tests. The error that I again saw is that browser releases the camera automatically. I can't understand why browser leaves the camera captured stream suddenly.
Why can we not put traps in the browser logic to debug this?
This is very critical to fix.
Is this happening with Ubuntu browser ONLY? or we have seen this in Windows Chrome browser?
We should focus on Windows ONLY - Ubuntu does not have any market share and I do not want to chase Ubuntu Browser issues
Also is number of quality issues we had is related to you using Ubuntu? When did you switched to Ubuntu?
I have tested it with interns today. We tested many use cases in this but this error was not reproduced.
This had happened with me when I was using two tabs to test conference. In this, both tabs had released the camera capture.
Today, I tested it again on two tabs but it didn't release the camera capture. This happens sometimes when I am using same browser for 2 participants.
@sojharo This is clearly an intermittent issue. So the key is to understand when it happens and do we have enough debug logs to capture it?
Has this happened to somebody else besides you? If so then we should continue to work on it.
If this is only happening to you on Ubuntu / Chrome browser then I would downgrade it.
For our meeting please start using Windows vs. Ubuntu.
I tested again with Sumaira's MAC and my linux. At first, the camera got released on ubuntu. In further tests, the camera was not released. However, on Mac no such error occurred. I had tested with windows vs linux too with interns. It seems to me that the problem is on my computer. As sumaira also said that she has never noticed any such problem of releasing the camera.
Thanks for the investigation. I am lowering the priority, You should report it on Chrome group user group.
We have choppy sounds sometimes and most of the times can't share the screen in conference of 4 people.
I would do tests in this and look into logs.