search

OpenBazaar / OpenBazaar-Server

(Deprecated) OpenBazaar 1.0 Server daemon for communication with OpenBazaar-Client
MIT License
608 stars 173 forks source link

Segfault on app close, very long response time after a while #343

Open pryds opened 8 years ago

pryds commented 8 years ago

Not entirely sure if this is a server issue. If not, please inform me, and I'll create the issue appropriately.

Brief Description: After OB has been running for a while, sometimes hours, sometimes minutes, the GUI becomes more and more unresponsive, and it seems that other users can't connect to my node. When I close down the server+client from the GUI, I get a segmentation fault in the terminal window showing server messages. After that, a "ps ux" still shows running OB processes for several minutes, while it sounds like the HDD is working on overtime. Edit: After more testing, it turns out that the segfault and running processes are an issue, even if the app has not become unresponsive.

Operating System (OS and version): Ubuntu 14.04 LTS OpenBazaar version: 1.1.1 installed from 64 bit .deb file. Hardware: Intel i7, 16 GB RAM

Reproducible (Always / Almost Always / Sometimes / Rarely / Couldn't Reproduce): Almost always

Steps to reproduce:

  1. Start server+client combo by typing "openbazaar" in terminal.
  2. Wait. Sometimes for hours, sometimes a minute, until client starts to become unresponsive.
  3. Close down server+client by clicking on weird coloured round button in upper left corner.

Observed Behavior: GUI disappears right away. Terminal window prints:

Closing Application
Shutting down server daemon
Segmentation fault (core dumped)

then releases to bash. Full debug.log here: http://pasted.co/d59dac1a

For several minutes after this, OB processes keep running -- sometimes just a minute, sometimes I had to kill all processes after 10 minutes. During this time, it sounds like the HDD has a lot of work to do. A ps ux reveals this as e.g.:

thomas@barks:~$ ps ux | grep openbazaar 
thomas   19489  0.0  0.0 289712 14120 pts/4    S    20:41   0:00 /usr/share/openbazaar/openbazaar --type=zygote --no-sandbox
thomas   19523  2.0  0.0      0     0 pts/4    Z    20:41   0:02 [openbazaar] <defunct>
thomas   19534  2.8  0.2 319968 45064 pts/4    Dl   20:41   0:03 /usr/share/openbazaar/resources/app/../OpenBazaar-Server/openbazaard start --loglevel debug -p 33321
thomas   20227  0.0  0.0  17408   920 pts/4    S+   20:43   0:00 grep openbazaar

Expected Behavior: Client + server close down cleanly without segfaults.

Additional info (links, images, etc go here): debug.log: http://pasted.co/d59dac1a

pryds commented 8 years ago

After more testing, it seems that I don't have to wait for the GUI to become unresponsive.

After having run the server+client combo for app. 12 hours, the GUI didn't seem unresponsive this time, but I had problems connecting to other people's listings. I don't know whether this and the unresponsiveness is related to the segfault or not.

On the other hand, I found out that I am able to reproduce the segfault and processes that keep running after the GUI is closed down nearly every time I try -- even if it has been running for just a minute or two.

algor1th commented 8 years ago

I am observing the same problem on a thinkpad x220 Intel I5 2500m 2 core / 4 threads 10 gb ram. The operating system is Ubuntu 16.04 LTS kernel 4.4 Openbazaard is also showing high cpu utilization