Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Electrum 2.9.3 OS X Crash sending transaction #2728

Closed
ghost opened this issue Aug 11, 2017 · 13 comments
Closed

Electrum 2.9.3 OS X Crash sending transaction #2728

ghost opened this issue Aug 11, 2017 · 13 comments

Comments

@ghost
Copy link

ghost commented Aug 11, 2017

When trying to send a transaction the Electrum 2.9.3 (OS X Sierra) app crashes - reverted to version 2.9.2 - works fine.
The problem seems to happen only when trying to send or preview a new transaction. The problem still happens after reinstalling the Electrum 2.9.3 and even when cleaning up all the contents of the ~/.electrum folder

@ecdsa
Copy link
Member

ecdsa commented Aug 11, 2017

sorry about that.
I made a new dmg file; an you try it and let me know if it is fixed?

@pmitchev
Copy link

Not fixed, just downloaded and tried

@ecdsa
Copy link
Member

ecdsa commented Aug 11, 2017

I cannot reproduce that.
is there any error message in the osx console?

@azteke
Copy link

azteke commented Aug 12, 2017

I'm experiencing the same issue. It also crashes when I press the command key when the cursor is blinking in the 'Pay to' field. (cannot paste a bitcoin address using command-v).

@ecdsa
Copy link
Member

ecdsa commented Aug 12, 2017

is there any error message in the osx console?

@pmitchev
Copy link

This is the only thing I am getting on "electrum" search in console. I hope it helps:

[Electrum pid 48900 mux-aware] exiting, non-mux-aware app count 0, runtime: 0:02:43.774

@ghost
Copy link
Author

ghost commented Aug 12, 2017

@ecdsa I think the problem can be the new "icons"... but I am no specialist. The problem can be reproduced by simple pressing the Command key at the Send dialog, just like @azteke said.

Running from OS X terminal gives me the message when app crashes:

Illegal instruction: 4

For debugging I am attaching the Apple Error Report
Electrum_2_9_3_crash_Sierra.txt

The most relevant message, in my opinion:

Notes: Translocated Process

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [0]

@philrosenthal
Copy link

I am able to reproduce this on my Mac Pro desktop, but not on my Macbook Pro.

Both running the same 2.9.3 version.

@rex4539
Copy link
Contributor

rex4539 commented Aug 17, 2017

100% reproducible here too.

  1. Click on Send tab.
  2. Press the Command key on keyboard.

Electrum_2017-08-17-173748_MacBook-Pro-2011.txt

@rex4539
Copy link
Contributor

rex4539 commented Aug 17, 2017

Running on the debugger gives the following:

* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0) frame #0: 0x00000001072dc354 QtGui.so___lldb_unnamed_symbol10595$$QtGui.so + 94
QtGui.so`___lldb_unnamed_symbol10595$$QtGui.so:
-> 0x1072dc354 <+94>: bextrl %edx, 0x8(%rcx), %ebx
0x1072dc35a <+100>: movq %rax, %rdi
0x1072dc35d <+103>: callq 0x1072f2aa8 ; symbol stub for: PyEval_RestoreThread
0x1072dc362 <+108>: movq %rbx, %rdi
Target 0: (Electrum) stopped.
(lldb) bt

(lldb) disassemble
QtGui.so`___lldb_unnamed_symbol10595$$QtGui.so:
0x1072dc2f6 <+0>: pushq %rbp
0x1072dc2f7 <+1>: movq %rsp, %rbp
0x1072dc2fa <+4>: pushq %r14
0x1072dc2fc <+6>: pushq %rbx
0x1072dc2fd <+7>: subq $0x20, %rsp
0x1072dc301 <+11>: leaq -0x28(%rbp), %rcx
0x1072dc305 <+15>: movq %rdi, (%rcx)
0x1072dc308 <+18>: leaq -0x20(%rbp), %rdi
0x1072dc30c <+22>: movq $0x0, (%rdi)
0x1072dc313 <+29>: leaq 0x226ed6(%rip), %r14 ; sipAPI_QtGui
0x1072dc31a <+36>: movq (%r14), %rbx
0x1072dc31d <+39>: leaq 0x156bac(%rip), %rax ; sipExportedTypes_QtGui
0x1072dc324 <+46>: movq 0x17a8(%rax), %r8
0x1072dc32b <+53>: leaq 0x4dcac(%rip), %rdx ; "'B'"
0x1072dc332 <+60>: leaq -0x18(%rbp), %r9
0x1072dc336 <+64>: xorl %eax, %eax
0x1072dc338 <+66>: callq *0x280(%rbx)
0x1072dc33e <+72>: testl %eax, %eax
0x1072dc340 <+74>: je 0x1072dc36c ; <+118>
0x1072dc342 <+76>: callq 0x1072f2aae ; symbol stub for: PyEval_SaveThread
0x1072dc347 <+81>: movq -0x18(%rbp), %rcx
0x1072dc34b <+85>: movq 0x20(%rcx), %rcx
0x1072dc34f <+89>: movl $0x10f, %edx ; imm = 0x10F
-> 0x1072dc354 <+94>: bextrl %edx, 0x8(%rcx), %ebx
0x1072dc35a <+100>: movq %rax, %rdi
0x1072dc35d <+103>: callq 0x1072f2aa8 ; symbol stub for: PyEval_RestoreThread
0x1072dc362 <+108>: movq %rbx, %rdi
0x1072dc365 <+111>: callq 0x1072f2a6c ; symbol stub for: PyBool_FromLong
0x1072dc36a <+116>: jmp 0x1072dc397 ; <+161>
0x1072dc36c <+118>: movq (%r14), %rax
0x1072dc36f <+121>: movq -0x20(%rbp), %rdi
0x1072dc373 <+125>: leaq 0x34ec6(%rip), %rdx ; sipStrings_QtGui
0x1072dc37a <+132>: leaq 0x16750(%rdx), %rsi
0x1072dc381 <+139>: addq $0x15241, %rdx ; imm = 0x15241
0x1072dc388 <+146>: leaq 0x221fc1(%rip), %rcx ; sipTypeDef_QtGui_QWidget + 4008
0x1072dc38f <+153>: callq *0x2a0(%rax)
0x1072dc395 <+159>: xorl %eax, %eax
0x1072dc397 <+161>: addq $0x20, %rsp
0x1072dc39b <+165>: popq %rbx
0x1072dc39c <+166>: popq %r14
0x1072dc39e <+168>: popq %rbp
0x1072dc39f <+169>: retq

@mpollow
Copy link

mpollow commented Aug 17, 2017

Same issue here, it crashes when trying to paste the recipient address.

Attached the Console output.

Electrum_2017-08-17-002000_macbookpro-235.crash.txt

@dawatz
Copy link

dawatz commented Aug 19, 2017

fixed by reverting to 2.9.2

@ghost
Copy link

ghost commented Oct 19, 2017

This is still an issue with 2.9.3 & macOS 10.12.6 (16G29)

UPDATE gist with a few crash reports: https://gist.github.com/BM5k/78538618416d94f8adf9c033ca1dde1f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants