FATAL assert_same_rec
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
STR:
- checkout my branch of m-c: https://github.com/fitzgen/gecko-dev/tree/heap-snapshots-e10s-copy
$ ./mach build$ ./mach xpcshell-test toolkit/devtools/heapsnapshot/tests/unit_ipc/test_saveHeapSnapshot_e10s_01.js --debugger rr$ rr replay(gdb) continue
This gist has my full rr replay session that led up to the assertion failure, as well as conecting gdb to rr and dumping rr's backtrace: https://gist.github.com/fitzgen/04d8d34ca7d059c59d13
My rr is built from this commit:
commit a7f6a951d58d61a56a31dcff262e27024fa40aee
Author: Robert O'Callahan <robert@ocallahan.org>
Date: Wed Sep 16 15:08:53 2015 +1200
Print errno name when assertion fails.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure using the listed mach, rr, and gdb commands, then read the linked gist and backtrace alongside the assert_same_rec failure. The issue provides no named source file or test beyond toolkit/devtools/heapsnapshot/tests/unit_ipc/test_saveHeapSnapshot_e10s_01.js; done means identifying the failure's cause and a concrete path to address it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100