Skip to content
This repository was archived by the owner on Jan 24, 2025. It is now read-only.

Nil pointer in WarpSync #452

Closed
karimodm opened this issue Oct 20, 2023 · 3 comments
Closed

Nil pointer in WarpSync #452

karimodm opened this issue Oct 20, 2023 · 3 comments
Labels
bug Something isn't working non-actionable
Milestone

Comments

@karimodm
Copy link
Contributor

karimodm commented Oct 20, 2023

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0xc17dcc]

goroutine 1022729 [running]:
github.com/iotaledger/iota-core/pkg/protocol/chainmanager.(*Chain).LatestCommitment(0xc0000001f0?)
        /scratch/pkg/protocol/chainmanager/chain.go:54 +0x2c
github.com/iotaledger/iota-core/pkg/protocol.(*BlockDispatcher).warpSyncIfNecessary(0xc000646000, 0xc08eea6200, 0xd2066ec365257924?)
        /scratch/pkg/protocol/block_dispatcher.go:352 +0x8c
github.com/iotaledger/iota-core/pkg/protocol.(*BlockDispatcher).monitorLatestEngineCommitment.func1(0xc0ba02b9e0)
        /scratch/pkg/protocol/block_dispatcher.go:400 +0xfe
github.com/iotaledger/hive.go/runtime/event.(*Event1[...]).Trigger.func1(0xc07d0c1320?)
        /go/pkg/mod/github.com/iotaledger/hive.go/[email protected]/event/events.go:88 +0x177
github.com/iotaledger/hive.go/ds/orderedmap.(*OrderedMap[...]).ForEach(0xd3baaf, 0xc001a376f8?)
        /go/pkg/mod/github.com/iotaledger/hive.go/[email protected]/orderedmap/orderedmap.go:130 +0xc4
github.com/iotaledger/hive.go/runtime/event.(*Event1[...]).Trigger(0x0?, 0x0?)
        /go/pkg/mod/github.com/iotaledger/hive.go/[email protected]/event/events.go:70 +0x71
github.com/iotaledger/hive.go/runtime/event.(*Event1[...]).Trigger.func1(0xc05391dbf0?)
        /go/pkg/mod/github.com/iotaledger/hive.go/[email protected]/event/events.go:88 +0x177
github.com/iotaledger/hive.go/ds/orderedmap.(*OrderedMap[...]).ForEach(0xc0003f3a00, 0xc001a377f8?)
        /go/pkg/mod/github.com/iotaledger/hive.go/[email protected]/orderedmap/orderedmap.go:130 +0xc4
github.com/iotaledger/hive.go/runtime/event.(*Event1[...]).Trigger(0xc0ba02b9e0?, 0xd2066ec365257924?)
        /go/pkg/mod/github.com/iotaledger/hive.go/[email protected]/event/events.go:70 +0x71
github.com/iotaledger/iota-core/pkg/protocol/engine/notarization/slotnotarization.(*Manager).createCommitment(0xc000175d40, 0x1f0)
        /scratch/pkg/protocol/engine/notarization/slotnotarization/manager.go:266 +0xe6f
github.com/iotaledger/iota-core/pkg/protocol/engine/notarization/slotnotarization.(*Manager).tryCommitSlotUntil(0xc000175d40, 0x1fa)
        /scratch/pkg/protocol/engine/notarization/slotnotarization/manager.go:166 +0x92
github.com/iotaledger/iota-core/pkg/protocol/engine/notarization/slotnotarization.(*Manager).tryCommitUntil(0xc000175d40, 0x1fa)
        /scratch/pkg/protocol/engine/notarization/slotnotarization/manager.go:106 +0x45
github.com/iotaledger/iota-core/components/protocol.provide.func1.NewProvider.func15.1.1(0xc001a37ed8?)
        /scratch/pkg/protocol/engine/notarization/slotnotarization/manager.go:69 +0x131
github.com/iotaledger/hive.go/runtime/event.(*Event1[...]).Trigger.func1.1()
        /go/pkg/mod/github.com/iotaledger/hive.go/[email protected]/event/events.go:86 +0x1f
github.com/iotaledger/hive.go/runtime/workerpool.(*Task).run(0xc08ffa24b0)
        /go/pkg/mod/github.com/iotaledger/hive.go/[email protected]/workerpool/task.go:48 +0x72
github.com/iotaledger/hive.go/runtime/workerpool.(*WorkerPool).workerReadLoop(0xc06c0a6620)
        /go/pkg/mod/github.com/iotaledger/hive.go/[email protected]/workerpool/workerpool.go:190 +0x25
github.com/iotaledger/hive.go/runtime/workerpool.(*WorkerPool).worker(0xc06c0a6620)
        /go/pkg/mod/github.com/iotaledger/hive.go/[email protected]/workerpool/workerpool.go:170 +0x50
created by github.com/iotaledger/hive.go/runtime/workerpool.(*WorkerPool).startWorkers in goroutine 238
        /go/pkg/mod/github.com/iotaledger/hive.go/[email protected]/workerpool/workerpool.go:162 +0x25
@karimodm karimodm converted this from a draft issue Oct 20, 2023
@karimodm karimodm added this to the 1.0 RC milestone Oct 20, 2023
@piotrm50 piotrm50 self-assigned this Nov 2, 2023
@piotrm50 piotrm50 moved this from Backlog to In Progress in iota-core Nov 2, 2023
@piotrm50 piotrm50 moved this from In Progress to Backlog in iota-core Nov 3, 2023
@piotrm50 piotrm50 moved this from Backlog to In Progress in iota-core Nov 3, 2023
@piotrm50 piotrm50 removed their assignment Nov 3, 2023
@piotrm50 piotrm50 moved this from In Progress to Backlog in iota-core Nov 3, 2023
@piotrm50
Copy link
Collaborator

piotrm50 commented Nov 3, 2023

Hopefully will not be an issue in reactive chain manager.

@karimodm karimodm added the bug Something isn't working label Nov 6, 2023
@karimodm
Copy link
Contributor Author

On hold because of #320

@jonastheis
Copy link
Contributor

Since the code around warp sync changed drastically in #320 and #568 (ChainManager and block dispatcher do not exist anymore) this can be closed.

@github-project-automation github-project-automation bot moved this from Backlog to Done in iota-core Dec 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working non-actionable
Projects
Archived in project
Development

No branches or pull requests

3 participants