--- Log opened Mon Mar 06 00:00:02 2023
01:02 -!- jespada [~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net] has joined #c-lightning
01:49 -!- jarthur [~jarthur@user/jarthur] has quit [Quit: jarthur]
05:14 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:19 -!- endothermicdev [~endotherm@2600:1700:8481:8900:a5f6:20d8:4068:7cf0] has quit [Remote host closed the connection]
05:20 -!- endothermicdev [~endotherm@2600:1700:8481:8900:7a55:4c7c:5ada:48be] has joined #c-lightning
05:52 < denis2342> endothermicdev: could the fix in #6068 fix explain my crashing problems?
07:48 < endothermicdev> @denis2342 I'm kind of doubtful it's related. The fix in #6068 would take the node running 3.5 days in order to do a pruning cycle, and that would have to be followed by a restart. Even then it doesn't crash, it just starts duplicating gossip_store entries.
07:48 < denis2342> ok
07:50 < denis2342> thought it could have to do with it because rusty said something about valgrind not catching something which means maybe memory reading at the wrong place which can lead to a segmentation fault
08:59 -!- jarthur [~jarthur@user/jarthur] has joined #c-lightning
09:03 -!- denis2342 [~denis@p4fd2bfa7.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds]
10:13 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 255 seconds]
14:09 -!- denis2342 [~denis@p4fd2bfa7.dip0.t-ipconnect.de] has joined #c-lightning
17:28 -!- function1 [~function1@user/function1] has quit [Quit: ZNC 1.8.2 - https://znc.in]
17:29 -!- function1 [~function1@user/function1] has joined #c-lightning
--- Log closed Tue Mar 07 00:00:03 2023