spesmilo / spesmilo/electrum

Crash on exit (PyQt, Qt, abnormal termination, quit, segfault, SIGSEGV)

Open
#6,889 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug 🐞 pull-request wanted 📣 Qt ✨
Dominant language
Python
Stars
8.6k
Forks
3.5k
Avg merge
2d 8h
Merged PRs (30d)
61

Description

On 4.0.9 (but this was also present in previous versions) if you normally close Electrum (both stand alone and installed version) on this OS you will get an abnormal crash.

OS: Windows 7 Ultimate 32 bit
(updates to date)
It's quite easy to reproduce, just normally start electrum , leave it on for few minutes and then normally try to close it from the close button. It will immediately pop-up this (in 8/10 cases):

ele2

Here is the full dump:

roblem Event Name:	BEX
  Application Name:	electrum-4.0.9.exe
  Application Version:	0.0.0.0
  Application Timestamp:	00000000
  Fault Module Name:	StackHash_0a9e
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	00000000
  Exception Offset:	1e175f42
  Exception Code:	c0000005
  Exception Data:	00000008
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	1033
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Reproduce the exit crash on Windows 7 32-bit using the standalone and installed Electrum builds, then trace the shutdown path using the supplied crash dump. Done means normal close completes without an abnormal termination or SIGSEGV.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.