Cannot solve problem with #issue 183 (100% CPU usage from Bitmessage) #592
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm on a mac 10.5.8. I have python 2.7 and I run Bitmessage through Terminal. The thing works and connects ok except the CPU usage that climbs up to 190% from the very first moment.... It keeps on for hours...Even when Bitmessage stops processing messages and public keys. I have read the previous closed threads but they seem no use to me... When I make the additions to the .py file the terminal cannot run Bitmessage anymore. I tried to copy the whole file (class_receiveDataThread.py)and replace mine and then Bitmessage opened but with no ability of communicating. In fact I sent some messages that waited forever for aknowledgment and nobody received them...
I can't understand what goes wrong... Also I want to mention that my file class_receiveDataThread.py seems to be very different. What could I do to solve this???
Here is its content:
doTimingAttackMitigation = True
import time
import threading
import shared
import hashlib
import socket
import random
from struct import unpack, pack
import sys
import string
from subprocess import call # used when the API must execute an outside program
from pyelliptic.openssl import OpenSSL
import highlevelcrypto
from addresses import *
import helper_generic
import helper_bitcoin
import helper_inbox
import helper_sent
from helper_sql import *
import tr
from debug import logger
from bitmessagemain import shared.lengthOfTimeToLeaveObjectsInInventory, shared.lengthOfTimeToHoldOnToAllPubkeys, shared.maximumAgeOfAnObjectThatIAmWillingToAccept, shared.maximumAgeOfObjectsThatIAdvertiseToOthers, shared.maximumAgeOfNodesThatIAdvertiseToOthers, shared.numberOfObjectsThatWeHaveYetToGetPerPeer, shared.neededPubkeys
This thread is created either by the synSenderThread(for outgoing
connections) or the singleListenerThread(for incoming connections).
class receiveDataThread(threading.Thread):
If there are differences between what you have on your computer and what is on Github, a good place to start would be to move the program to some other directory and get a good copy of the code off of Github again.
Thanks for the response Atheros1, but can you be a bit more specific? I have the PyBitmessage folder on my Desktop.Any other place would ok? How will that help anyway?
Edit: I did what you said, but nothing changed... Still with the "solved issue" code , It seems that i m connected, CPU usage is very low, but when I send a message to any of my contacts, it says "message sent.waiting on acknowledgment" but the ack never comes... Also in the network status tab NO messages are processed, NO public keys, nothing at all. Dot is yellow. Any more ideas????????
@ariscampis OS X 10.5 appears unsupported since 2011. But just in case, can you retry with the latest code? In general, Bitmessage should be working on OSX.
I now have a Mac with a fresh install of OSX 10.11 and it works fine. The computer isn't even that fast, it's a Mac Mini Early 2009 with a Core 2 Duo. Please try either the latest master branch, or the unofficial mailchuck fork: https://github.com/mailchuck/PyBitmessage/releases/tag/v0.5.2