Bitmessage/PyBitmessage-2025-02-21
Archived
2
0
Fork 0
Code Issues 167 Pull Requests 54 Actions Packages Projects Releases 5 Wiki Activity

Trouble sending on multicor machines on 0.4.4 #725

New Issue
Closed
opened 2014-10-14 00:33:55 +02:00 by grant-olson · 2 comments
grant-olson commented 2014-10-14 00:33:55 +02:00 (Migrated from github.com)
Copy Link

I've seen this on both an OSX box (8 cores) and a linux box (4 cores). I was only able to do the full reproducible on linux, as my keys.dat file prevented me from going back to 0.4.3 on the OSX box.

  1. Check out v0.4.3.
  2. Open top
  3. Open bitmessage.
  4. Send a message.
  5. Processes will start up for each core in top to calculate the PoW more quickly. Message will send.
  6. Close bitmessage.
  7. Check out ProtoV3
  8. Send a message.
  9. Processes will fire up in top. They'll consume 100% cpu for a few minutes. One by one, the CPU usage on each process will drop to zero.
  10. The bitmessage app will still say that we're doing work to calculate the PoW. The message never sends.
I've seen this on both an OSX box (8 cores) and a linux box (4 cores). I was only able to do the full reproducible on linux, as my `keys.dat` file prevented me from going back to 0.4.3 on the OSX box. 1. Check out v0.4.3. 2. Open top 3. Open bitmessage. 4. Send a message. 5. Processes will start up for each core in top to calculate the PoW more quickly. Message will send. 6. Close bitmessage. 7. Check out `ProtoV3` 8. Send a message. 9. Processes will fire up in top. They'll consume 100% cpu for a few minutes. One by one, the CPU usage on each process will drop to zero. 10. The bitmessage app will still say that we're doing work to calculate the PoW. The message never sends.
grant-olson commented 2014-10-14 20:35:34 +02:00 (Migrated from github.com)
Copy Link

That worked. I'll get a new OSX binary up shortly...

That worked. I'll get a new OSX binary up shortly...
Atheros1 commented 2014-10-14 20:36:47 +02:00 (Migrated from github.com)
Copy Link

Excellent

Excellent
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working as it's supposed to
build
Related to building or build system
dependencies
Pull requests that update a dependency file
developers
The issue is relevant mainly for developers rather than users
documentation
duplicate
enhancement
New feature
formatting
Code or UI text formatting
invalid
legal
mobile
Frontend for mobile devices (kivy)
obsolete
packaging
performance
protocol
Protocol change
question
refactoring
regression
Some issue, fixed in the past, appears again
security
test
translation
usability
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
PeterSurda
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-02-21#725
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?