blocks|key|2799931|text|[VM]+(scriptId)没有特殊的含义。它是一个虚拟名称，用来帮助我们区分与文件名没有直接关联的代码，比如使用eval和friends创建的代码。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2799932|在过去，所有这些脚本都被贴上了(program)的标签。|2799933|如果您感兴趣，只要使用look+up+"[VM]"in+the+source+code+of+Chromium，您就会发现这些数字在开发人员工具之外没有任何重要意义。|2799934|更新2015-06-25|2799935|[VM]+(scriptId)已重命名为VMscriptId+a+while+ago，下面是direct+link+to+search+result，以防值再次更改。|2799936|entityMap|0|LINK|mutability|MUTABLE|url|https://code.google.com/p/chromium/codesearch#search/&q=%2522%255BVM%255D%2522&sq=package:chromium&type=cs|1|https://chromiumcodereview.appspot.com/23530041|2|https://chromium.googlesource.com/chromium/blink/%2B/669a2f29610ca8d0a8790bb829bfde4ba768e936/Source/devtools/front_end/bindings/DefaultScriptMapping.js#193^0|0|F|1M|4|0|F|9|0|J|6|B|18|0|0|0|0|F|K|A|V|B|1|1A|S|2|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@$9|1A|A|1B|1|1C]]|E|$]]|$1|J|3|K|5|6|7|1D|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]]|D|@$9|1J|A|1K|1|1L]|$9|1M|A|1N|1|1O]]|E|$]]|$1|N|3|-4|5|6|7|1P|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]|V|$5|Q|R|S|E|$T|W]]|X|$5|Q|R|S|E|$T|Y]]]]

<code>[VM] (scriptId)</code> has no special meaning. It's a dummy name to help us to distinguish code which are not directly tied to a file name, such as code created using <code>eval</code> and friends.

In the past, all of these scripts were just labelled <code>(program)</code>.

If you're interested, just <a href="https://code.google.com/p/chromium/codesearch#search/&amp;q=%22%5BVM%5D%22&amp;sq=package:chromium&amp;type=cs" rel="noreferrer">look up <code>"[VM]"</code>in the source code of Chromium</a>, you will discover that these numbers have no significant meaning outside the developer tools.

<h2>update 2015-06-25</h2>

<code>[VM] (scriptId)</code> was renamed to <code>VMscriptId</code> <a href="https://chromiumcodereview.appspot.com/23530041" rel="noreferrer">a while ago</a>, and here is the <a href="https://chromium.googlesource.com/chromium/blink/+/669a2f29610ca8d0a8790bb829bfde4ba768e936/Source/devtools/front_end/bindings/DefaultScriptMapping.js#193" rel="noreferrer">direct link to search result</a> in case the value changes again.

blocks|key|3012306|text|当使用eval时，javascript被抛到Chrome调试器VM中。为了查看在Chrome+Debugger源码下使用eval创建的js，在js的末尾(感谢Splaktar)设置此属性：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3012307|//@+sourceURL=dynamicScript.js|code-block|syntax|javascript|3012308|Is+possible+to+debug+dynamic+loading+JavaScript+by+some+debugger+like+WebKit,+FireBug+or+IE8+Developer+Tool?|offset|length|3012309|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1705952/is-possible-to-debug-dynamic-loading-javascript-by-some-debugger-like-webkit-fi^0|0|0|0|30|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

When using eval, the javascript gets thrown into the Chrome Debugger VMs. In order to view js created with eval under Chrome Debugger Sources, set this attribute at the end (thanks Splaktar) of the js:

<pre><code>//@ sourceURL=dynamicScript.js
</code></pre>

<a href="https://stackoverflow.com/questions/1705952/is-possible-to-debug-dynamic-loading-javascript-by-some-debugger-like-webkit-fi">Is possible to debug dynamic loading JavaScript by some debugger like WebKit, FireBug or IE8 Developer Tool?</a>

blocks|key|3012344|text|每当你通过AJAX加载HTML内容，并且内容包含<script>标签时，脚本将使用eval()进行计算，并被Chrome的Sources视图识别为以'VM‘开头的新文件。您可以随时转到Network选项卡，找到AJAX请求，并查看整个HTML响应，包括您的脚本。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3012345|entityMap^0|O|8|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Whenever you load HTML content through AJAX, and that content contains <code>&lt;script&gt;</code> tags, the script will be evaluated using eval() and recognized by Chrome's Sources view as a new file beginning with 'VM'. You can always go to the Network tab, find the AJAX request, and view the HTML response in its entirety, including your script.

blocks|key|3012412|text|如果你想在chrome中调试以编程方式注入的JS文件，你可以使用debugger;语句，这比查找脚本所在位置更快，也比用sourceurl生成文件更快。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3012413|它的工作原理就像一个断点，无论你在哪里使用debugger;语句，它都会自动在chrome+source选项卡中定位你的代码。|3012414|​|3012415|📷|atomic|3012416|3012417|请注意，脚本的源是VMXXX文件。|3012418|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statement|1|https://developers.google.com/web/updates/2013/06/sourceMappingURL-and-sourceURL-syntax-changed#sourceurl|2|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/b85feca32f6c87bdb5946b9b5a3399ca.png|imageAlt^0|W|9|W|9|0|1O|9|1|0|L|9|0|0|0|1|2|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@$9|18|A|19|1|1A]|$9|1B|A|1C|1|1D]]|E|$]]|$1|F|3|G|5|6|7|1E|8|@$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1H|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1I|8|@]|D|@$9|1J|A|1K|1|1L]]|E|$]]|$1|M|3|I|5|6|7|1M|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1N|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1O|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W]]|X|$5|S|T|U|E|$V|Y]]|Z|$5|10|T|11|E|$12|13|14|-4]]]]

If you want to debug programmatically injected JS files in chrome you can use the <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statement" rel="noreferrer"><code>debugger;</code></a> statement, this is faster than finding where your script is and also faster than generating a file with <a href="https://developers.google.com/web/updates/2013/06/sourceMappingURL-and-sourceURL-syntax-changed#sourceurl" rel="noreferrer">sourceurl</a>.

It works like a breakpoint and automaticaly pinpoints your code in the chrome source tab wherever you use the <code>debugger;</code> statement.

<a href="https://i.stack.imgur.com/tONvF.png" rel="noreferrer"><img src="https://i.stack.imgur.com/tONvF.png" alt="Debugger;"></a>

Note that the source of the script is a VMXXX file.

blocks|key|3012357|text|我发现一些Chrome扩展生成了VM+-它们将CSS/JS插入到页面中，然后Chrome使用VM文件来运行它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3012358|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 found VM gets generated from some Chrome extensions - they insert CSS/JS into the page and Chrome uses the VM files to run it.

blocks|key|3012369|text|当你调试一个子窗口(iframe)源文件时，它随后被卸载，你的源文件也会得到VM前缀和黄色背景。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3012370|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|$]]

When you're debugging a child window (iframe) source which is subsequently unloaded your source file will also get the VM prefix and the yellow background.

blocks|key|3012376|text|我遇到了同样的问题。问题是，我的应用程序的代码被意外地认为是黑盒。当我试图进入代码时，它一直在打开这些VMXXXX选项卡。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3012377|删除应用程序的js文件的黑盒设置后，我可以成功地单步执行我的代码。|3012378|entityMap^0|1F|6|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

I ran into the same problem. The issue is that my app's code was considered blackboxes by accident. When I tried to step into the code, it kept opening these <code>VMXXXX</code> tabs.

After removing the blackbox setting for my app's js file, I could successfully step through my code.

blocks|key|184074|text|我在调试我的angular应用程序时也遇到了同样的问题。看到太多无法黑箱的VM脚本，真的需要很长时间才能调试。我宁愿选择mozilla/IE+explorer进行调试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|184075|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 had the same issue when I was debugging my angular application. Seeing too many VM scripts which could not be blackboxed were really taking long to debug. 
I rather chose mozilla/IE explorer to debug.

blocks|key|2800154|text|为了防止这种情况|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2800155|(function+()
+{
++var+originalEval+=+eval;
++eval+=
+++function+(script)
+++{
++++return+originalEval(script+%2B+"\n//#+sourceURL=blackbox-this.js");
+++}
+}());|code-block|syntax|javascript|2800156|然后是blackbox+%5E.*blackbox-this.js$|offset|length|style|CODE|2800157|当setInterval/setTimeout获得字符串时，它也是如此(但这不是一个好的做法，对吧？；)|2800158|这对你有效吗？|2800159|entityMap^0|0|0|C|K|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

for prevent this 

<pre><code>(function ()
 {
 var originalEval = eval;
 eval =
 function (script)
 {
 return originalEval(script + "\n//# sourceURL=blackbox-this.js");
 }
 }());
</code></pre>

And then blackbox <code>^.*blackbox-this.js$</code>

Same for setInterval/setTimeout when it gets a string (but that is a bad practice anyway, right? ;))

Does that work for you?

I added a breakpoint in my javascript file (jaydata.js) and was pressing "Step over to the next function call."
When it got to a line that was:

<pre><code>},
</code></pre>

another file titled "[VM] (8312)" popped up. I kept clicking "Step over to the next function call" and now my screen is:

<img src="https://i.stack.imgur.com/bG9B8.png" alt="enter image description here"> 

What are these strange and mysterious scripts titled "[VM](XXXX " and where do they come from?

Chrome Development Tool: [VM] file from javascript

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我在javascript文件(jaydata.js)中添加了一个断点，并按下了"Step over to the next function call“。当它到达一行时，它是：},弹出了另一个标题为"“的文件。我一直点击“跳到下一个函数调用”，现在我的屏幕是：​这些名为"VM(XXXX )“的奇怪而神秘的脚本是什么?它们是从哪里来的？

问Chrome开发工具: javascript中的[VM]文件
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Chrome开发工具: javascript中的[VM]文件EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Chrome开发工具: javascript中的[VM]文件
EN