rpc memory leak

[happyshares]

We had the same issue. A workaround for now is to use the http rpc port and add the path "/rpc" to your requests.

[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

[pharesim]

Now I don't get the expected response from some rpc calls.
Filed an issue:
https://github.com/BitShares/bitshares_toolkit/issues/536

[santaclause102]

probably unrelated but similar: https://bitsharestalk.org/index.php?topic=5750.msg77873#msg77873

[pharesim]

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.

[fuzzy]

 

[pharesim]

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.