Some third-party crash bugs are closed too eagerly
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
E.g. https://bugzilla.mozilla.org/show_bug.cgi?id=1290403, the signature simply switched to another address of the same DLL.
Maybe the script, when the signature is a DLL, should remove the address part for the search.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the linked Bugzilla case and the script that processes crash signatures, focusing on how DLL signatures retain their address during searches. Done means a signature that only changes to another address in the same DLL is not treated as a new third-party crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100