electrumx crashed with general protection fault ip:50fcc4 sp:7ffcc2465108 error:0 in python3.7[421000+232000]
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 568
- Forks
- 447
- PR merge metrics
- No merged PRs in 30d
Description
Electrumx has been running for 2d 11h and crashed. Dmesg:
[Tue Sep 15 08:43:16 2020] traps: electrumx_serve[3171321] general protection fault ip:50fcc4 sp:7ffcc2465108 error:0 in python3.7[421000+232000]
Electrumx log has nothing interesting:
2020-09-15 08:43:12,097:INFO:ElectrumX:[2771418] disconnected whilst throttled
2020-09-15 08:43:12,099:INFO:ElectrumX:[2771413] disconnected whilst throttled
2020-09-15 08:43:12,099:INFO:ElectrumX:[2771415] disconnected whilst throttled
2020-09-15 08:43:12,107:INFO:ElectrumX:[2771414] disconnected whilst throttled
2020-09-15 08:43:12,167:INFO:ElectrumX:[2771412] disconnected whilst throttled
2020-09-15 08:43:12,175:INFO:ElectrumX:[2771425] SSL 14.185.171.91:54000, 283 total
System:
OS: Debian GNU/Linux 10 (buster) x86_64
Kernel: 5.7.0-0.bpo.2-amd64
Electrum straight from git, latest commit:
commit 9ca59facfdb50daf063a5813fc9b08eb6fa1b246 (HEAD -> master, origin/master, origin/HEAD)
Merge: 148df48 23633c2
Author: ghost43 <somber.night@protonmail.com>
Date: Mon Aug 24 17:30:54 2020 +0000
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 reported dmesg entry and the ElectrumX log around the crash, then compare the stated Debian, kernel, Python 3.7, and ElectrumX commit details. Collect enough diagnostic information to identify a reproducible cause; the issue is not complete until the crash is explained and a verified fix or reproduction is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100