05:21:10 <sech1> selsta moneromooo wfaressuissia I got this crash again: https://paste.debian.net/hidden/6b06edc2/
05:21:54 <sech1> anything else I can do in gdb before I kill the process? I'll wait for a few hours.
05:23:00 <selsta> it seems to be the race fixed in https://github.com/monero-project/monero/pull/7873
05:24:21 <selsta> I think you can close it and recompile latest release-v0.17
05:24:59 <selsta> still don't know why it gets triggered so frequently on your machine
05:27:32 <sech1> Now I need to understand how the fix works
05:28:02 <sech1> I mean, it removed "std::vector<cryptonote::blobdata> fluff_txs;" alltogether, but where it was used?
05:28:38 <selsta> btw you can use gcore inside gdb to save the core file so that you don't have to keep it open
05:28:57 <selsta> though don't remember the exact command
05:30:40 <sech1> so the fix moved "fluff_txs" from p2p connection to a separate struct, ok
05:33:02 <sech1> it crashes so often probably because of slow HDD + purged node. It was a full node before but it didn't crash.
05:33:25 <sech1> maybe also because p2pool connects to it and ZMQ is activated
05:34:53 <sech1> the difference with my other stable node is HDD/SSD and purged/full
05:38:49 <sech1> building latest release-v0.17, I'll run it under gdb for a few days too
05:39:16 <sech1> to make sure that the fix actually fixes the crash. My server is a perfect "Canary" :D
08:25:23 <wfaressuissia> `node_server: add race condition demo` all these demos are reproducing with almost 100% probability fixed problem for debug/release build
08:26:05 <wfaressuissia> so anyone can run that demo under gdb without fix to know what was the problem
09:44:12 <monerobull[m]> 17.3 is getting prepared, i assume we're getting it 1st of November, right?
11:59:59 <selsta> luigi1111: merges today?
12:58:21 <luigi1111> yes
17:56:04 <fluffypony> 2021-10-25 15:49:22.034 I SYNCHRONIZED OK
17:56:04 <fluffypony> free(): corrupted unsorted chunks
17:56:04 <fluffypony> Aborted
17:56:12 <fluffypony> just had a long-ish running Linux node die
17:56:26 <fluffypony> moneromooo: something you're aware of or should I see if it dumped?
17:57:41 <wfaressuissia> `free(): corrupted unsorted chunks` very interesting, any info ?
17:57:50 <fluffypony> this is on v0.17.2.3-release btw
17:58:13 <wfaressuissia> anything in dmesg /journalctl ?
17:58:50 <fluffypony> it was running in a screen session, so nothing in journalctl
17:58:58 <fluffypony> dmesg looks normal too
18:00:07 <wfaressuissia> how screen may hide abnormally terminated processes from journalctl ? gdb - yes, screen/tmux - likely no
18:05:19 <wfaressuissia> "dmesg looks normal too" it's probably normal, so no info without coredump then
18:06:29 <moneromooo> That's a bad bug and needs a fix.
18:39:04 <fluffypony> bah - no coredumps enabled
18:39:31 <fluffypony> wfaressuissia: sorry I saw journalctl and read systemd, my brain is on the fritz today
18:45:09 <fluffypony> journalctl looks clean too
18:45:11 <fluffypony> I've turned dumps on
18:45:15 <fluffypony> will see if it happens again
21:44:20 <hendursaga> Fingerprint is still 81AC 591F E9C4 B65C 5806  AFC3 F0AF 4D46 2A0B DF92 right?
21:45:39 <moneromooo> Part of your message is missing (the part where you say what that fingerprint is meant be for).
23:52:44 <luigi1112> .merges
23:52:44 -xmr-pr- 7995 7996 8002 8003 8004 8006 8007 8011 8018 8019 8022