2.5.0 中未处理的异常

Question

卸载两个集合后，ArangoDB 2.5.0 异常终止：

2015-03-20T14:59:58Z [9436] ERROR Unhandled exception: -1073741819

现在会崩溃。

有人知道出了什么问题吗？

提前致谢！

2015-05-18 更新：详细日志模式显示：

2015-05-18T07:10:50Z [1724] ERROR encountered out-of-memory error
2015-05-18T07:10:50Z [1724] ERROR JavaScript exception in file 'd:/Program Files
/ArangoDB/ArangoDB 2.5.3/share/arangodb/js/server/modules/org/arangodb/arango-st
atement.js' at 86,45: [ArangoError 3: out of memory (while executing)]
2015-05-18T07:10:50Z [1724] ERROR !  var result = AQL_EXECUTE(this._query, this.
_bindVars, opts);
2015-05-18T07:10:50Z [1724] ERROR !                                            ^

2015-05-18T07:10:50Z [1724] ERROR stacktrace: Error: out of memory (while execut
ing)\n  at Error (native)\n  at ArangoStatement.execute (d:/Program Files/Arango
DB/ArangoDB 2.5.3/share/arangodb/js/server/modules/org/arangodb/arango-statement
.js:86:45)\n  at d:/Program Files/ArangoDB/ArangoDB 2.5.3/share/arangodb/js/serv
er/modules/org/arangodb/foxx/queues/manager.js:66:12\n  at Array.forEach (native
)\n  at db._executeTransaction.action (d:/Program Files/ArangoDB/ArangoDB 2.5.3/
share/arangodb/js/server/modules/org/arangodb/foxx/queues/manager.js:43:34)\n  a
t [object ArangoDatabase].ArangoDatabase._executeTransaction (d:/Program Files/A
rangoDB/ArangoDB 2.5.3/share/arangodb/js/server/modules/org/arangodb/arango-data
base.js:142:10)\n  at Object.exports.manage (d:/Program Files/ArangoDB/ArangoDB
2.5.3/share/arangodb/js/server/modules/org/arangodb/foxx/queues/manager.js:37:6)
\n  at eval (<anonymous>:2:51)\n  at eval (<anonymous>:3:7)\n  at eval (<anonymo
us>:3:19)\n


#
# Fatal error in ..\..\src\heap\mark-compact.cc, line 2137
# CHECK(success) failed
#
2015-05-18T07:10:52Z [1724] ERROR Unhandled exception: -1073741819 - will crash
now.

Answer 1

嗯，它没有出现在我们的 AMD64 Windows Server 2012 R2 上。

你可以安装procdump吗（https://docs.arangodb.com/3.11/operations/installation/compiling/compile-on-windows/） 这样我们就可以获得更多信息？

procdump -accepteula -e -ma <process ID of the arangod> c:\tmp\core.dmp

（进程 ID 在您的日志文件中的括号中，在上面的事件中它应该是 9436）

Procdump 将捕获此异常，并写入转储文件。