On Thu, Apr 28, 2016 at 7:14 PM, Jan de Mooij <[email protected]> wrote: > > Having only a few signatures for all of our JIT crashes conflates a lot of > different issues (imagine what would happen if most graphics or DOM crashes > had the same signature). Hopefully bug 1268029 will help a bit there.
It looks like that will categorize each JIT crash into one of the following five categories, is that right? #define ERROR_MAP(_) \ _(UNKNOWN) \ _(CORRUPT_CODE) \ _(EIP_IN_BETWEEN) \ _(BAD_BRANCH_TARGET) \ _(BAD_EIP_INSTRUCTION) \ Five isn't many, but it's better than one :) Is the EIP_IN_BETWEEN one just for detecting the infamous AMD bug, or does that problem occur in other cases as well? > How feasible would it be to give (part of) SpiderMonkey its own malloc heap? > There are heap fragmentation and memory use concerns, but we could use this > only on Nightly or only on 64 bit... Doing it only on Nightly doesn't seem wise -- it would just mask problems until a later date. Nick _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
