Bug 16366 - "Unsafe JavaScript" spew to console takes up CPU constantly while page loaded
Summary: "Unsafe JavaScript" spew to console takes up CPU constantly while page loaded
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore JavaScript (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.5
: P2 Major
Assignee: Nobody
URL: http://sovietcomputing.com/node/2
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2007-12-09 04:58 PST by Mark Rowe (bdash)
Modified: 2010-01-02 10:06 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Rowe (bdash) 2007-12-09 04:58:29 PST
After loading the URL, http://sovietcomputing.com/node/2, in Safari 3 or TOT warnings similar to the following are written to the JavaScript console and system console repeatedly:

Unsafe JavaScript attempt to access frame with URL http://gmodules.com/ig/ifr?url=http://www.hitsalive.com/google_gadgets/russian_wotd.xml&up_promo22=1&up_promo6=1&up_numuses=0&synd=open&w=120&h=200&title=Russian+-+Audio+Word+of+the+Day&border=%23ffffff%7C0px%2C1px+solid+%23993333%7C0px%2C1px+solid+%23bb5555%7C0px%2C1px+solid+%23DD7777%7C0px%2C2px+solid+%23EE8888&source=http%3A%2F%2Fsovietcomputing.com%2Frobots.txt%23resize_iframe%2526remote_iframe_0%2526140%24#idi_hr=http%3A%2F%2Fsovietcomputing.com%2Frobots.txt from frame with URL http://sovietcomputing.com/robots.txt#resize_iframe%26remote_iframe_0%26140$. Domains, protocols and ports must match.

The warnings continue to be displayed many times per second until the page is closed.  Safari's CPU usage spikes dramatically over that which is typical when viewing a page.
Comment 1 Mark Rowe (bdash) 2007-12-10 00:23:55 PST
<rdar://problem/5638289>
Comment 2 Geoffrey Garen 2007-12-11 10:03:06 PST
How do you know that the warnings are the source of the CPU usage? It seems to me that CPU is consumed by the script that is executing.
Comment 3 Mark Rowe (bdash) 2007-12-11 11:55:44 PST
I don't.  I suspect that the warnings are merely a symptom of whatever is also causing the CPU usage.  In other browsers I do not see the CPU usage nor the constant warnings.
Comment 4 Adam Barth 2010-01-02 10:06:15 PST
This site no longer exists.  I think there is (or used to be) a real bug here, but there's not enough information in this report to track it down.  :(