Unhandled Exception in 2.5.0 - arangodb

Question

After unloading two collections, ArangoDB 2.5.0 terminated with exception:
2015-03-20T14:59:58Z [9436] ERROR Unhandled exception: -1073741819
will crash now.
Does anybody know what went wrong?
Thanks in advance!
Update 2015-05-18: verbose-log-mode shows this:
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

Hm, it doesn't appear here on our AMD64 Windows Server 2012 R2.
Can you install procdump ( https://docs.arangodb.com/cookbook/CompilingUnderWindows.html )
so we can get a little more information?
procdump -accepteula -e -ma <process ID of the arangod> c:\tmp\core.dmp
(the process id is in your logfile in the brackets, it would have been 9436 in your incident above)
Procdump will catch this exception, and write a dump file.