blocks|key|276372|text|我已经注意到，如果我禁用缓存，我不会再在控制台中得到这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|276373|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have noticed that if I disable the cache, I no longer get this error in the console.

blocks|key|272925|text|检查代码中是否存在重复的meta+cache-control，并删除其中之一：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|272926|<meta+http-equiv="cache-control"+content="no-cache"+/>|code-block|syntax|javascript|272927|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Check your code for duplicated meta cache-control and remove one of them:

<pre><code>&lt;meta http-equiv="cache-control" content="no-cache" /&gt;
</code></pre>

blocks|key|3192735|text|如果Firebug+(在我的例子中是1.8)被禁用，则不会出现该错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3192736|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The error doesn't occur if Firebug (in my case 1.8) is disabled.

blocks|key|276459|text|我注意到，如果在文档加载完成后使用document.write写入文档(例如，在从JQuery的$(+document+).ready()方法调用的函数中)，则会发生此错误。当这种情况发生时，Firefox似乎会丢弃旧文档，并编写一个新文档。我不知道这是不是新的行为。似乎当你试图对旧文档进行操作时，例如使用JQuery选择器，你会得到这个错误。对我来说，修复有问题的脚本使其在文档加载后不调用document.write修复了错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|276460|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've noticed that this error can happen if you write to the document with document.write after the document has completed loading (e.g. in a function called from JQuery's $(document).ready() method). When this happens, it seems that Firefox discards the old document and writes a new one. I don't know if this is new behavior or not. It seems that when you try to operate on the old document, e.g. with JQuery selectors, you get this error. For me, fixing the script in question to not call document.write after the document had loaded fixed the error.

blocks|key|2979138|text|在我的例子中，是document.write方法在Windows的Firefox4、5、6上导致了这个问题。Linux版本不受影响。我要做的就是重写document.write方法。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2979139|我知道现在不应该使用document.write，但是由Sun/Oracle编写的标准Java+Applet部署脚本deployJava.js正在使用它。谷歌在谷歌AdSense广告中使用了它。document.write无处不在。|2979140|<script>
++++var+documentWriteOutput+=+'';
++++var+got+=+document.write;
++++document.write+=+function(arg)+{+documentWriteOutput+%2B=+arg;+}
</script>
<script+src="badScriptThatIsUsingDocumentWrite.js"></script>
<script>
++++runBadScriptThatIsUsingDocumentWrite();
++++document.write+=+got;
++++//+Do+whatever+you+want+with+the+documentWriteOutput
++++//+e.g.+$('#somewhere').html(documentWriteOutput);
</script>|code-block|syntax|javascript|2979141|我希望这能帮到你。然而，我在互联网上看到了很多“解决方案”，这些解决方案对我来说都不起作用。这可能意味着“试图在已清除的作用域上运行编译并运行脚本”是一个Firefox+JavaScript引擎问题/错误。|2979142|entityMap^0|8|E|22|E|0|A|E|1M|D|2P|E|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|13|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|P|$]]

In my case, it was <code>document.write</code> method causing the problem on Firefox 4, 5, 6 on Windows. Linux versions are unaffected. What I had to do is to overwrite <code>document.write</code> method.

I aware that <code>document.write</code> shouldn't be used these days, but <code>deployJava.js</code>, a standard Java Applet deployment script written by Sun/Oracle, is using it. Google is using it in Google AdSense ads. <code>document.write</code> is everywhere.

<pre><code>&lt;script&gt;
 var documentWriteOutput = '';
 var got = document.write;
 document.write = function(arg) { documentWriteOutput += arg; }
&lt;/script&gt;
&lt;script src="badScriptThatIsUsingDocumentWrite.js"&gt;&lt;/script&gt;
&lt;script&gt;
 runBadScriptThatIsUsingDocumentWrite();
 document.write = got;
 // Do whatever you want with the documentWriteOutput
 // e.g. $('#somewhere').html(documentWriteOutput);
&lt;/script&gt;
</code></pre>

I hope this helps. However, I saw lots of "solutions" on the Internet that didn't work for me. It may mean that "Attempt to run compile-and-go script on a cleared scope" is a Firefox JavaScript engine problem/bug.

blocks|key|3192839|text|我也有这个问题，但我做了一个干净的FireFox重新安装。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3192840|在那之后，错误就消失了。|3192841|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

i had this problem too but I did a clean re-installation of FireFox. 

after that the error was gone.

blocks|key|3192853|text|当我尝试在从同一域iframe附加的元素上添加事件时，我得到了这个错误。已添加clone()和已停止错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3192854|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got this error when I tried adding events on elements appended from a same domain iframe. Added clone() and errors stopped.

blocks|key|278493|text|对于我(Firefox11，Firebug1.9.1)来说，它有时会在我刷新页面(+F5或CTRL%2BF5)后发生，而调试器在断点处暂停。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|278494|解决方案似乎是继续执行脚本，只有当Firebug+is+而不是+paused时，才会刷新页面。|offset|length|style|BOLD|278495|entityMap^0|0|S|3|W|6|14|7|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|I|$]]

For me (Firefox 11, Firebug 1.9.1) it happens sometimes after I refresh the page (either F5 or CTRL+F5) while debugger is paused on a breakpoint.

The solution seems to be to continue the execution of the script, and refresh the page only when Firebug is not paused.

blocks|key|276500|text|这与firebug没有任何关系。当firebug被禁用时，它“消失”的原因是您不再看到异常。出现这种情况的原因是将一个处理程序附加到一个事件，该事件现在为空，但未正确清除。您需要确保正确处理该处理程序，否则该事件仍会激发对该处理程序的引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|276501|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It has nothing to do with firebug. The reason it "goes away" when firebug is disabled is that you are no longer seeing the exception. The cause of this is having an handler attached to an event that is now null but not properly cleaned up. You need to make sure that handler is properly disposed of, otherwise the event still fires the reference to the handler.

blocks|key|276503|text|它是:菜单Firebug+->控制台->显示Chrome错误|type|unstyled|depth|inlineStyleRanges|entityRanges|data|276504|关闭，故事结束;)|276505|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It is: menu Firebug -> Console -> Show Chrome Errors

switch off, end of story ;)

Since upgrading to Firefox 4.0, I've noticed that I'm occasionally getting an error in the console stating:

<blockquote>
 attempt to run compile-and-go script on a cleared scope
</blockquote>

The only information I can find about this on the net currently is on the <a href="http://groups.google.com/group/mozilla.dev.platform/browse_thread/thread/10ff69b04b88e06f" rel="noreferrer">mozilla groups forum</a>, where it is suggested that it's something to do with session restoring. In my case, though I haven't been able to reliably reproduce the error, it happens at any time, not just after a restore.

What's the deal? How do I stop the error?

Error: Attempt to run compile-and-go script on a cleared scope

调试器

Windows

Linux

Java

自从升级到Firefox 4.0后，我注意到我偶尔会在控制台上收到一个错误消息：尝试在清除的作用域上运行编译并运行脚本我目前能在网上找到的关于这个的唯一信息是在上，在那里有人建议它与会话恢复有关。在我的例子中，虽然我不能可靠地重现错误，但它在任何时候都会发生，而不仅仅是在恢复之后。怎么回事？如何停止该错误？

问错误:尝试在清除的作用域上运行编译并运行脚本
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问错误:尝试在清除的作用域上运行编译并运行脚本EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问错误:尝试在清除的作用域上运行编译并运行脚本
EN