New issue
Advanced search Search tips

Issue 609825 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Very small setInterval timeout values lockup broker process

Reported by ch...@huntresslabs.com, May 6 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36

Steps to reproduce the problem:
1. Visit this URL: http://www.pcsystemcare.info/error/lki45n4/
2. Try to click other tabs after the audio starts and the popup is visible

What is the expected behavior?
The user can still select other tabs as well as close the current tab.

What went wrong?
After looking at the page source it looks like the only thing really going on here is that the setInterval() callback to display an alert is being fired every 10ms. But since there is only ever 1 alert displayed at a time the process must be getting hung up processing and rejecting all the alert calls. But I could be totally off here.

It doesn't appear this site is doing anything else malicious other than trying to get the user to call an antivirus phishing scammer.

I've attached the page source in case the URL doesn't work in the future.

Did this work before? N/A 

Chrome version: 49.0.2623.110  Channel: stable
OS Version: Fedora release 23 (Twenty Three)
Flash Version: Shockwave Flash 21.0 r0
 
broker_hang.html
8.0 KB View Download
This behavior doesn't reproduce on my Linux box but does still affect my Windows box running Chrome 50.0.2661.94 m.

Stopping this is as simple as clicking the box to not allow the page to open anymore popups and then closing the tab but many users will likely be confused and stuck since their browser locks up.
Components: -UI UI>Browser>SafeBrowsing Internals>Cast>UI
Cc: a...@chromium.org
avi -- Do you want to dup this bug with one you have?

Comment 4 by a...@chromium.org, May 9 2016

Status: WontFix (was: Unconfirmed)
There is no bug to dup this against. This is standard stuff, and WAI.

Closing as WontFix.

Sign in to add a comment