All users were logged out of Bugzilla on October 13th, 2018
Please provide a STR.
I don't have STR as the issue doesn't happen persistently.
triage: I'm afraid we can't + it without being able to reproduce it. Could you provide some more information?
blocking-b2g: 2.1? → -
Assignee: nobody → gsvelto
Target Milestone: --- → 2.1 S7 (24Oct)
Doug, the error is not easily reproducible and after spending quite some time I couldn't produce STR. I am still seeing the error 1/20 times I run my test script. Could you point me to the file that might be throwing this error, I can add some debug message on console.trace() to possibly help debug?
I believe that the error is somewhere in this file: https://github.com/mozilla-b2g/gaia/blob/master/shared/js/dialer/tone_player.js
waiting for anshul to see if he has more logs to investigate this further per comment #4,5.
I think this might be caused by a race condition whereas we trash the audio context and then try to play. See bug 834530 comment 50 of why this might be happening. The changes I'm doing in that bug should prevent those races so it might be worth re-testing this after that bug lands.
See Also: → bug 834530
Whiteboard: [caf priority: p2][CR 741215] → [caf priority: p2][CR 741215][planned-sprint c=]
Target Milestone: 2.1 S7 (24Oct) → 2.1 S8 (7Nov)
Whiteboard: [caf priority: p2][CR 741215][planned-sprint c=] → [caf priority: p2][CR 741215][planned-sprint c=3]
Anshul, could you try the patches in bug 834530 and see if they fix the issue here? That would be attachment 8508778 [details] [diff] [review] and attachment 8511646 [details] [diff] [review].
Toggling needinfo off and on again for visibility.
Doug I am not able to reproduce this error anymore even without the patch. I am marking this issue closed for now.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
Thanks for checking. I could definitely be wrong here, but I strongly suspect that bug 1079810 fixed this.
Resolution: WORKSFORME → DUPLICATE
Duplicate of bug: 1079810
You need to log in before you can comment on or make changes to this bug.