Why / where is the error "Permission denied for <http://ad.yieldmanager.com> to call the Location.toString method"

Question

EDIT: I added clarification in response to the comment; where possible and meaningful, those added improvements are made in italics.

I posted this question in Firefox groups, and also here on SO.

There are at least 25 related questions on SO, a few representative questions:

• Flash error
• cross-domain problem
• just a secret
• FF XPCOM Problem

There are ~ 15 accepted answers, none of which seem to apply here. Since there are so many questions and accepted answers, I assume that my question addresses a problem that developers often stumbled over.

I wrote a direct web page, which, in my opinion, is absolutely normal and ordinary. I have nothing unusual on the page, nothing that I, and probably you and all the web developers, have at least not used in the last ten years.

I am viewing a page that I developed with Firefox 3.6.16 with Firebug 1.6.2.

At various intervals, but usually every 30-60 minutes for 65% of incidents, an error message appears in the Firebug console:

Permission denied for <http://ad.yieldmanager.com> to call method Location.toString 

Most of these posts point to yieldmanager, but I see complaints about doubleclick and interclick. FB does not give me any error properties.

View-> Page Source shows nothing about a limiter or any other criminal.

There are calls for adsense, but deleting this code doesn’t change anything in error messages.

There are about 3,000 lines of plain, vanilla JavaScript on the page, but nothing exotic that I see.

I did not explicitly or (I suppose) implicitly include any framework code: no JScript, xjs, MooTools, nothing.

Question:. How to find out who is calling Location.toString (); and how can i get rid of this guy?

Answer 1

This may not happen to you at all, however, keep in mind that firebug will display error messages in your console if you open another window and go to the site with these calls. In short, these errors cannot be related to your page.

Answer 2

In my comment, try disabling extensions (safe mode) and check the Firebug XHR checkbox if you haven't already.