New issue
Advanced search Search tips

Issue 740151 link

Starred by 3 users
Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
jmukthavaram@chromium.org
altimin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

window.setTimeout is not firing when XSplit Broadcaster software is running/recording.

Reported by sergeuy....@gmail.com, Jul 7 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. attempt to execute any code that sets timeout (window.setTimeout) WHILE Xsplit Broadcaster software is running (version 29.1701.1640)
2. time out function won't fire and no error/exception visible.
3. attempt to do the same with Edge browser - code works as expected

What is the expected behavior?
setTimeout should work regardless of external apps running?

What went wrong?
the setTimout function fails to execute code and does not throw errors

some other triage notes:
- if I switch my app to use touch emulation in Chrome - the event fires normally.
- I will update Xspplit broadcaster now and see if the results are the same

Did this work before? N/A 

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 10.0
Flash Version: 

here is a little video:
https://www.youtube.com/watch?v=bB9luP87tJE&feature=youtu.be

Comment 1 by sergeuy....@gmail.com, Jul 7 2017 

Update:
- updated to the latest version of Xsplit broadcaster - same issue
- discovered that if you (while Xsplit is recording) switch to touch emulation then the code fires off as expected.

https://www.youtube.com/watch?v=OAbVuSwGdA8&feature=youtu.be

Comment 2 by schenney@chromium.org, Jul 7 2017

Components: -Blink Blink>DOM

Comment 3 by hayato@chromium.org, Jul 10 2017

Components: -Blink>DOM Blink>HTML
window.setTimeout -> HTML

Comment 4 by tkent@chromium.org, Jul 11 2017

Components: -Blink>HTML Blink>Scheduling

Comment 5 by jmukthavaram@chromium.org, Jul 19 2017

Cc: jmukthavaram@chromium.org
Labels: Needs-Feedback
sergeuy.rudenko@,
Thanks for filing the issue.
Could you please provide us any sample test /html file to triage the issue from TE end.

Comment 6 by skyos...@chromium.org, Jul 24 2017 

Could you see if starting Chrome with the --disable-background-timer-throttling makes a difference here?

Comment 7 Deleted

Project Member

Comment 8 by sheriffbot@chromium.org, Jul 24 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 9 by ranjitkan@chromium.org, Jul 26 2017

Labels: Needs-Milestone

Comment 10 by ajha@chromium.org, Aug 1 2017

Labels: Needs-Feedback
Friendly ping to get an update on this as per C#5 and C#6.

Comment 11 by hdodda@chromium.org, Nov 7 2017

Status: WontFix (was: Unconfirmed)
Marking it as won't fix as there is no update from user from long period. Please feel free to raise a new issue if any issues in latest chrome channels.

Thanks!
►

Sign in to add a comment