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.

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

Panic crash #410

Closed
navaneeth opened this issue Aug 4, 2022 · 3 comments
Closed

Panic crash #410

navaneeth opened this issue Aug 4, 2022 · 3 comments

Comments

@navaneeth
Copy link

  • Which Faktory package and version? - 1.5.1
  • Which Faktory worker package and version? - Running as Docker container in k8s
  • Please include any relevant worker configuration
    • Golang based workers
    • 3 worker processes
  • Please include any relevant error messages or stacktraces
panic: signal: killed

goroutine 17 [running]:
github.com/contribsys/faktory/storage.bootRedis.func2(0xc00012c420, 0xc00001c120, 0x11)
	/Users/mikeperham/src/github.com/contribsys/faktory/storage/redis.go:159 +0x10d
created by github.com/contribsys/faktory/storage.bootRedis
	/Users/mikeperham/src/github.com/contribsys/faktory/storage/redis.go:155 +0xfc5

Are you using an old version? - 1.5.1

@mperham
Copy link
Collaborator

mperham commented Aug 4, 2022 via email

@navaneeth
Copy link
Author

Looks like Faktory process was running out of memory. Raised the memory limit and it seems to fix it. I see the memory usage growing consistently. Is there a leak happening?

image

@mperham
Copy link
Collaborator

mperham commented Aug 4, 2022

It does us no good to talk of a memory leak in an old version. I need to know if the memory leak is in the latest version, 1.6.1.

@mperham mperham closed this as completed Oct 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants