rollup_sync_service: invalid memory address or nil pointer dereference

[pc-quiknode]

System information

Geth version: scrolltech/l2geth:scroll-v5.8.23

Steps to reproduce the behaviour

upgrade sepolia node to v5.8.23

Backtrace

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0xd4c11e]
goroutine 4267 [running]:
github.com/scroll-tech/go-ethereum/rollup/rollup_sync_service.(*RollupSyncService).updateRollupEvents(0xc003943360, {0xc01a409400?, 0x5, 0x20101004bccab?})
        github.com/scroll-tech/go-ethereum/rollup/rollup_sync_service/rollup_sync_service.go:290 +0x89e
github.com/scroll-tech/go-ethereum/rollup/rollup_sync_service.(*RollupSyncService).fetchRollupEvents(0xc003943360)
        github.com/scroll-tech/go-ethereum/rollup/rollup_sync_service/rollup_sync_service.go:207 +0x20d
github.com/scroll-tech/go-ethereum/rollup/rollup_sync_service.(*RollupSyncService).Start.func1()
        github.com/scroll-tech/go-ethereum/rollup/rollup_sync_service/rollup_sync_service.go:147 +0x1f4
created by github.com/scroll-tech/go-ethereum/rollup/rollup_sync_service.(*RollupSyncService).Start in goroutine 1
        github.com/scroll-tech/go-ethereum/rollup/rollup_sync_service/rollup_sync_service.go:135 +0xcf

[Thegaram]

Thank you for reporting this. Did this happen on all your nodes or just some of them? Did the node recover after this?