Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

node-agent got "panic: runtime error: invalid memory address or nil pointer dereference" #403

Open
nashtsai opened this issue Dec 3, 2024 · 1 comment
Open

node-agent got "panic: runtime error: invalid memory address or nil pointer dereference" #403

nashtsai opened this issue Dec 3, 2024 · 1 comment

Comments

@nashtsai
Copy link

nashtsai commented Dec 3, 2024

node-agent is crashing, check attached stack error.

coroot node-agent version: 1.22.2
OS: Debian (5.4.210-amd64)

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

goroutine 242 [running]:
github.com/coroot/coroot-node-agent/containers.(*Process).Close(0xc001d06380)
	/tmp/src/containers/process.go:105  0x3c
github.com/coroot/coroot-node-agent/containers.(*Container).onProcessExit(0xc000a68780, 0x20df650?, 0x0)
	/tmp/src/containers/container.go:434  0x96
github.com/coroot/coroot-node-agent/containers.(*Registry).handleEvents(0xc000b11ef0, 0xc0008eb680)
	/tmp/src/containers/registry.go:234  0x3fc
created by github.com/coroot/coroot-node-agent/containers.NewRegistry in goroutine 1
	/tmp/src/containers/registry.go:124  0x685
@def def mentioned this issue Dec 3, 2024
Closed
@apetruhin
Copy link
Member

@nashtsai
I don't see how this line could cause the panic, as p is always non-nil here. Are you using our build of node-agent? It looks like a custom build that is panicking elsewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@apetruhin @nashtsai