KERN_INVALID_ADDRESS at 0x0000003100410020
Open
- Dominant language
- Python
- Stars
- 485
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
[postico.crash.txt](https://github.com/jakob/Postico/files/723375/postico.crash.txt)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the attached postico.crash.txt crash report and identify the failing component and call path associated with KERN_INVALID_ADDRESS. Reproduce the crash if the report provides enough context, then verify that the underlying fault is fixed and that the same crash no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100