if you look at the bad dump, the following sequence repeats for each url, in descending order (4 - 1), same as the good dump:Giorgio Maone wrote:I couldn't reproduce, but I based my (quite complex) fix on the assumption you were getting a totally random order, rather than DOM-parsing based, in nsIContentPolicy calls (something I could never observe, but I guessed could be a byproduct of your system's slowness).al_9x wrote:Did you repro or were you able to guess what it was?
Code: Select all
[NoScript] Content processing -- type: 5, location: http://url4.invalid/, origin: file:///C:/tmp/embedding.htm, ctx: <HTML Element>, mime: application/x-shockwave-flash, null
----------
[NoScript] Error()@:0
(5,[object XPCWrappedNative_NoHelper],[object XPCWrappedNative_NoHelper],[object XPCNativeWrapper],"application/x-shockwave-flash",null)@chrome://noscript/content/Policy.js:159
----------
[NoScript] [CP PASS 2] application/x-shockwave-flash*http://url4.invalid/, 5, null
----------
[NoScript] tagForReplacement
----------
[NoScript] Content BLOCKED Forbidden Content -- type: 5, location: http://url4.invalid/, origin: file:///C:/tmp/embedding.htm, ctx: <HTML Element>, mime: application/x-shockwave-flash, null
----------
[NoScript] Error()@:0
("Forbidden Content",[object Object])@chrome://noscript/content/Main.js:1862
(5,[object XPCWrappedNative_NoHelper],[object XPCWrappedNative_NoHelper],[object XPCNativeWrapper],"application/x-shockwave-flash",null)@chrome://noscript/content/Policy.js:619
the difference starts on the line after the above sequences
good:
Code: Select all
[NoScript] Adding plugin sites: ["http://url4.invalid", "http://url3.invalid", "http://url2.invalid", "http://url1.invalid"] to ["file://"]
Code: Select all
[NoScript] Adding plugin sites: ["http://url4.invalid", "http://url3.invalid"] to ["file://"]
