Author Topic: segfault in 0.4.19  (Read 4809 times)

0 Members and 1 Guest are viewing this topic.

Offline bytemaster

Re: segfault in 0.4.19
« Reply #45 on: October 02, 2014, 01:59:30 pm »
Updating to v0.4.19 seems reasonable to me. Segfault by itself isn't that much of a deal.
However bytemaster recommended not to update. Maybe he has other reasons?
There is still plenty of time for an informed decision. I suggest waiting for bytemaster's input and update to v0.4.19 as default option (if he is silent about this).

I agree. everyone downgrading would be very unpleasant.

There are no blockchain level bugs... we suspect that it may be low-memory machines that are crashing which is why we did not experience crashes in our own tests. 
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline bytemaster

Re: segfault in 0.4.19
« Reply #46 on: October 02, 2014, 02:01:45 pm »
Because downgrading is so unpleasant and we want the blockchain updates asap 

Dan & Eric are looking into the crash, but those that are experiencing it could you please report the specs of the machine you are running on?
Lets update to 0.4.19...    

For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline liondani

  • Hero Member
  • *****
  • Posts: 3719
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
Re: segfault in 0.4.19
« Reply #47 on: October 02, 2014, 02:01:48 pm »
that's a good example why the hard fork must have a bigger block distance from the initial announcement time ...

Sent from my ALCATEL ONE TOUCH 997D


Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12885
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: segfault in 0.4.19
« Reply #48 on: October 02, 2014, 02:02:45 pm »
hmmm .. 2GB is already low memory .. oha

three machines
XEN DomU - 2GB RAM - debian/archlinux - 64 bit
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline xfund

  • Full Member
  • ***
  • Posts: 148
    • View Profile
    • FUND投票基金
  • BitShares: xfund
Re: segfault in 0.4.19
« Reply #49 on: October 02, 2014, 02:05:18 pm »
0.4.19 ok
Asset:FUND

Offline bytemaster

Re: segfault in 0.4.19
« Reply #50 on: October 02, 2014, 02:07:15 pm »
hmmm .. 2GB is already low memory .. oha

Yes it is because we haven't taken time to optimize memory usage. 

We are keeping large portions of the blockchain database *IN RAM* for performance reasons and will probably continue to keep it in RAM long term.   Long-term light weight clients will not have the full chain and will therefore have a much smaller memory footprint and delegates can run machines with 128 GB of memory.   This will allow us to grow transaction volume and keep block latencies low.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline liondani

  • Hero Member
  • *****
  • Posts: 3719
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
Re: segfault in 0.4.19
« Reply #51 on: October 02, 2014, 02:08:30 pm »


Lets update to 0.4.19...

it will be an exciting night in Greece again ! Another pizza session will not heart me I guess  :)


Sent from my ALCATEL ONE TOUCH 997D


Offline Xeldal

  • Hero Member
  • *****
  • Posts: 1023
    • View Profile
  • BitShares: xeldal
Re: segfault in 0.4.19
« Reply #52 on: October 02, 2014, 02:11:13 pm »
experienced segfault
4GB RAM 

Offline bytemaster

Re: segfault in 0.4.19
« Reply #53 on: October 02, 2014, 02:13:04 pm »
experienced segfault
4GB RAM

So much for that theory... 4 GB should be more than enough.  What OS?
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline svk

Re: segfault in 0.4.19
« Reply #54 on: October 02, 2014, 02:13:40 pm »
Experienced segfaults on two different VPS: 1gb and 2gb of memory with 4gb of swap on both. Ubuntu 14.04
Worker: dev.bitsharesblocks

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
Re: segfault in 0.4.19
« Reply #55 on: October 02, 2014, 02:14:16 pm »
The segfaults I experienced were on the testing machine.
What I observe is about 2 GB memory consumption of v0.4.19 (RC1 had about 800 MB).
My primary configurations didn't have crashes so far.

UPDATE: Increased memory consumption might be related to DB reindexing. If you restart the client after reindexing is completed memory consumption goes back to normal
UPDATE2: Main system crashed also.
« Last Edit: October 02, 2014, 03:01:57 pm by emski »

Offline Xeldal

  • Hero Member
  • *****
  • Posts: 1023
    • View Profile
  • BitShares: xeldal
Re: segfault in 0.4.19
« Reply #56 on: October 02, 2014, 02:14:31 pm »
Ubuntu linux 14.04 x64

Offline liondani

  • Hero Member
  • *****
  • Posts: 3719
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
Re: segfault in 0.4.19
« Reply #57 on: October 02, 2014, 02:15:04 pm »


" ...and delegates can run machines with 128 GB of memory."

128 GB  ?

Sent from my ALCATEL ONE TOUCH 997D


Offline Xeldal

  • Hero Member
  • *****
  • Posts: 1023
    • View Profile
  • BitShares: xeldal
Re: segfault in 0.4.19
« Reply #58 on: October 02, 2014, 02:18:25 pm »
Code: [Select]
# free
             total       used       free     shared    buffers     cached
Mem:       4048312    3068232     980080        332     152304    2587972
-/+ buffers/cache:     327956    3720356

Offline bytemaster

Re: segfault in 0.4.19
« Reply #59 on: October 02, 2014, 02:18:39 pm »


" ...and delegates can run machines with 128 GB of memory."

128 GB  ?

Sent from my ALCATEL ONE TOUCH 997D

This is years from now... when we are processing 1000 transactions per second.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.