1. 主页
  2. 支持
技术文章 - CS268413

ThingWorx 服务器崩溃，错误信息为“内存不足：终止进程”。<Process ID> （Java）得分<score>或者献祭孩子”

已修改: 04-Mar-2026   


注意：本文已使用机器翻译软件翻译，以方便非英语客户阅读。但翻译内容可能包含语法错误或不准确之处。请注意， PTC对本文所含信息的翻译准确性及使用后果不承担任何责任。请在 此处 查看本文的英文原始版本以便参考。有关机器翻译的更多详情，请单击 此处 。
感谢您告诉我们。我们将尽快审阅此译文。

适用于

  • ThingWorx Platform 7.4 to 9.6

说明

  • ThingWorx 服务器启动失败
  • /var/log/messages.log中存在错误 
 Out of memory: Kill process <Process ID> (java) score <score> or sacrifice child kernel: java invoked oom-killer
  • Apache Tomcat 进程已停止
  • ThingWorx 应用服务器 CPU 使用率过高且存在访问问题
  • 重启后网址无法显示。
  • 应用程序已停止，状态为OOMKilled
  • hs_err_pid.log报告
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 2064 bytes for AllocateHeap
# Possible reasons:
#   The system is out of physical RAM or swap space
#   The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
# Possible solutions:
#   Reduce memory load on the system
#   Increase physical memory or swap space
#   Check if swap backing store is full
#   Decrease Java heap size (-Xmx/-Xms)
#   Decrease number of Java threads
#   Decrease Java thread stack sizes (-Xss)
#   Set larger code cache with -XX:ReservedCodeCacheSize=
#   JVM is running with Zero Based Compressed Oops mode in which the Java heap is
#     placed in the first 32GB address space. The Java Heap base address is the
#     maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
#     to set the Java Heap base and to place the Java Heap above 32GB virtual address.
  • ThingWorx 服务器频繁出现稳定性和性能问题，每天多次宕机，导致运营中断。


这是文章 268413 的 PDF 版本，可能已过期。最新版本 CS268413