blocks|key|3780040|text|OutOfMemoryError是一个例外，就像其他任何例外一样。它当然不会重启JVM。它可能会导致它所在的线程结束，但只有在它没有被捕获的情况下才会发生。您看到的可能不是核心转储，而仅仅是捕获的异常的堆栈跟踪，并使用e.printStackTrace()显式地打印它的堆栈跟踪。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3780041|entityMap^0|0|G|31|J|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

<code>OutOfMemoryError</code> is an exception just like any other. It certainly doesn't restart the JVM. It may possibly cause the thread in which it occurs to end, but that happens only if it is not caught anywhere. What you probably see is not a core dump, but merely the stack trace of the exception that was caught and its stack trace explicitly printed using <code>e.printStackTrace()</code>.

blocks|key|3780070|text|OutOfMemory只是一个错误，当一个对象由于缺乏可用内存而无法实例化时，就会抛出这个错误。这不会停止JVM，就像没有其他异常或错误一样。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3780071|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|$]]

OutOfMemory is just an Error that is thrown when an object could not be instanciated due to a lack of available memory. This does not stop the JVM, just like no other exception or error does.

blocks|key|2081783|text|Throwable永远不会重启JVM。OutOfMemoryError类似于所有其他运行时异常或错误:它传播调用堆栈，直到它被捕获。如果不是，则线程的UncaughtExceptionHandler通常通过终止线程并打印异常的堆栈跟踪来处理此异常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2081784|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|$]]

No Throwable ever restarts a JVM. The OutOfMemoryError is like every other runtime exception or error: it propagates the call stack until it's caught. And if it isn't, then the thread's UncaughtExceptionHandler handles this exception, usually by terminating the thread and printing the stack trace of the exception.

blocks|key|3690893|text|OutOfMemoryError或任何异常都不会重启JVM。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3690894|3690895|我看到发生OutOfMemoryError的行为，这不是从代码中捕获到的|blockquote|3690896|3690897|3690898|->+OutOfMemoryError继承java.lang.Error。错误描述了罕见或难以恢复的环境问题，例如计算机内存不足。您不需要处理Error类对象，但应该使用Throwable来处理它们。这些都应该被视为环境缺陷。|offset|length|style|CODE|3690899|在Exception+Hierarchy上看看吧。|3690900|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.oracle.com/javase/6/docs/api/java/lang/OutOfMemoryError.html|1|http://www.sentex.net/~pkomisar/J2/3_Exceptions.html^0|0|0|0|0|0|L|F|2D|9|3|G|0|0|1|J|1|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|11|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|14|8|@$J|15|K|16|L|M]|$J|17|K|18|L|M]]|9|@$J|19|K|1A|1|1B]]|A|$]]|$1|N|3|O|5|6|7|1C|8|@]|9|@$J|1D|K|1E|1|1F]]|A|$]]|$1|P|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|S|T|U|A|$V|Y]]]]

OutOfMemoryError or any exception never restart the JVM.

<blockquote>
 I am seeing a behavior where an OutOfMemoryError occurs this is not caught from the code 
</blockquote>

----> <a href="http://docs.oracle.com/javase/6/docs/api/java/lang/OutOfMemoryError.html" rel="nofollow">OutOfMemoryError</a> inherits <code>java.lang.Error</code>. Errors describe environmental problems which may be rare or difficult to recover from such as running out of computer memory. You are not expected to handle Error class objects but you should handle them with <code>Throwable</code>. These should be regarded as 
environmental flaws.

Have a look on <a href="http://www.sentex.net/~pkomisar/J2/3_Exceptions.html" rel="nofollow">Exception Hierarchy</a>.

blocks|key|2054591|text|OutOfMemoryError向一个线程报告其内存分配失败。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2054592|int+count+=+0;
long+start+=+System.currentTimeMillis();
for+(int+i+=+0;+i+<+10000000;+i%2B%2B)+{
++++try+{
++++++++long[]+longs+=+new+long[Integer.MAX_VALUE];
++++}+catch+(OutOfMemoryError+e)+{
++++++++count%2B%2B;
++++}
}
long+time+=+System.currentTimeMillis()+-+start;
System.out.printf("Got+%25,d+OutOfMemoryErrors+in+%25.1f+seconds%25n",+count,+time/1e3);|code-block|syntax|javascript|2054593|打印|2054594|Got+10,000,000+OutOfMemoryErrors+in+3.9+seconds|2054595|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

An OutOfMemoryError reports to one thread that its memory allocation failed.

<pre><code>int count = 0;
long start = System.currentTimeMillis();
for (int i = 0; i &lt; 10000000; i++) {
 try {
 long[] longs = new long[Integer.MAX_VALUE];
 } catch (OutOfMemoryError e) {
 count++;
 }
}
long time = System.currentTimeMillis() - start;
System.out.printf("Got %,d OutOfMemoryErrors in %.1f seconds%n", count, time/1e3);
</code></pre>

prints

<pre><code>Got 10,000,000 OutOfMemoryErrors in 3.9 seconds
</code></pre>

I always thought that an <code>OutOfMemoryError</code> restarts the JVM. 
But I am seeing a behavior where an <code>OutOfMemoryError</code> occurs this is not caught from the code (actually I don't even know if this is possible) 
and the <code>JVM</code> continues (a core dump is produced though). 
Can anyone help me understand this behavior?

OutOfMemoryError behavior in Java

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我一直认为OutOfMemoryError会重新启动虚拟机。但是我看到了一种行为，其中发生了OutOfMemoryError，这不是从代码中捕获的(实际上，我甚至不知道这是否可能)然后继续执行JVM (不过会产生一个核心转储)。有人能帮我理解这个行为吗？

问Java中的OutOfMemoryError行为
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Java中的OutOfMemoryError行为EN