Author Topic: rpc memory leak  (Read 2795 times)

0 Members and 1 Guest are viewing this topic.

Offline happyshares

  • Jr. Member
  • **
  • Posts: 33
    • View Profile
We had the same issue. A workaround for now is to use the http rpc port and add the path "/rpc" to your requests.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Just to complete that toic here a link to similar thread which also links to the memory leak:
https://bitsharestalk.org/index.php?topic=5562.new#new

Offline pharesim

  • Jr. Member
  • **
  • Posts: 29
    • View Profile
    • Horizon [HZ]
Now I don't get the expected response from some rpc calls.
Filed an issue:
https://github.com/BitShares/bitshares_toolkit/issues/536
Meet you on STEEM

Offline santaclause102

  • Hero Member
  • *****
  • Posts: 2486
    • View Profile

Offline pharesim

  • Jr. Member
  • **
  • Posts: 29
    • View Profile
    • Horizon [HZ]
Ok, seems I was really tired. Not sure how I managed to reproduce this all the time, there's definitely a memory leak which can be triggered by a HTTP POST. I got RPC working now though.

If you want me to try to reproduce the issue again tell me.
Meet you on STEEM

Offline fuzzy

WhaleShares==DKP; BitShares is our Community! 
ShareBits and WhaleShares = Love :D

Offline pharesim

  • Jr. Member
  • **
  • Posts: 29
    • View Profile
    • Horizon [HZ]
Is anyone else experiencing a memory leak with rpc calls?
My testing system runs an ubuntu 12.04 with 16GB RAM, the (command line) client works smooth.

As soon as the rpc call is made bitsharesx takes 100% cpu and fills up memory until the machine is unusable and needs a hard reset :-\
This also happens with a wrong user/password combination.
« Last Edit: July 20, 2014, 04:48:33 am by pharesim »
Meet you on STEEM