I would still assume it's because too much memory is getting allocated. When does this error occur now? How much memory is the process using when it happens?

- Maxime

Following Marc suggestion to execute d8 in gdb to be able to inspect the stack frame after the error, we found that the error originates from d8 in the garbage collector:

Generating machine code for: "ir/ast-to-ir.js"

Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000023 0x001ee138 in v8::internal::Map::CreateBackPointers () (gdb) bt #0 0x001ee138 in v8::internal::Map::CreateBackPointers () #1 0x001de423 in v8::internal::MarkCompactCollector::CreateBackPointers () Previous frame inner to this frame (gdb could not unwind past this frame)

I tried compiling d8 in debug mode but I still get the same error (the address was 0x0000000d for that run). For the record, Map::CreateBackPointers can be found in v8/src/objects.cc.

I am wondering if some of our extensions might not interact well with the gc.

Erick

---

Tachyon-list mailing list Tachyon-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/tachyon-list