segfault in 0.4.19

[bytemaster]

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

Yes... this is true.  Reindexing fills all of the database caches.

[emski]

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

[liondani]

It is not a memory issue, we have fixed the crash and notified DAC Sun.

read again folks 

Sent from my ALCATEL ONE TOUCH 997D

[xeroc]

It is not a memory issue, we have fixed the crash and notified DAC Sun.

That is good news .. I almost feared weekend hicking tour in fear of segfaults

[xeroc]

my delegate server is under real time monitoring, the RAM did reached to 80% yet before the client crashed,it may not due to the RAM size.

what software do you use for this? Couldn't get started monitoring my delegate machine(s) in more details

[crazybit]

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...

my delegate server is under real time monitoring, the RAM did NOT reached to 80% yet before the client crashed,it may not due to the RAM size.

[bytemaster]

It is not a memory issue, we have fixed the crash and notified DAC Sun.

[bytemaster]

" ...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.

[Xeldal]

Code: [Select]

# free
             total       used       free     shared    buffers     cached
Mem:       4048312    3068232     980080        332     152304    2587972
-/+ buffers/cache:     327956    3720356


[liondani]

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

128 GB  ?

Sent from my ALCATEL ONE TOUCH 997D

[Xeldal]

Ubuntu linux 14.04 x64

[emski]

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.

[svk]

Experienced segfaults on two different VPS: 1gb and 2gb of memory with 4gb of swap on both. Ubuntu 14.04

[bytemaster]

experienced segfault
4GB RAM

So much for that theory... 4 GB should be more than enough.  What OS?

[Xeldal]

experienced segfault
4GB RAM