Samuel Smith

bad_alloc sounds like memory exhaustion. Try allocating more swap space. You could also reduce the cache sizes via your electrum.conf hist_cache, utxo_cache and addr_cache settings.

I have seen the same problem. There is an unhandled exception that is output to the console but not the log files. Here is an example: ``` Exception in thread...

Found another unhandled exception that kills a thread: ``` Exception in thread Thread-4: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 763, in...

Yet another unhandled exception that kills the TCP thread: ``` Exception in thread Thread-8: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "build/bdist.linux-x86_64/egg/electrumserver/stratum_tcp.py", line 243,...

It looks to me that this error originated in bitcoind. What is in your .bitcoin/debug.log when this happens? You may have to reindex bitcoind.

In my case I'm using python3.7 rather than python3, so the update recipe is: ``` python3.7 -m pip uninstall electrumx python3.7 -m pip install . ``` I was previously using...

The user typed a filename with '/' in it. This is not a valid filename character on Windows. Perhaps user input should be sanitized to strip/replace characters that are not...

I see the same crash on Windows 10 (64 bit) with 32GB of ram. Definitely not due to "low ram". Notice the StackHash in the detail. That is an indication...