You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Was looking for a go lib to handle worker pools (after attempting to make my own with limited success), found this lib and it looked very promising. Seemed to run fine locally (running on Mac OS), but when I built it for our production servers (Ubuntu 18), I encountered this Unaligned 64-bit atomic operation error whenever we try to submit a task to the pool.
Have you encountered this before/am I just doing something wrong? Here is the code on my side:
Pool setup
maxWorkers := Conf.MaxFetcherWorkers
workQueueBufferSize := Conf.FetcherWorkQueueBufferSize
panicHandler := func(err interface{}) {
l.Logf("Fetcher worker exits from a panic: %v\nStack trace: %s", err, string(debug.Stack()))
}
workerPool := pond.New(maxWorkers, workQueueBufferSize, pond.PanicHandler(panicHandler))
l.Logf("Creating worker pool with max size=%v and workQueueBufferSize=%v", maxWorkers, workQueueBufferSize)
Hey @dave-filion! Interesting, first time I see this error. Did some quick research and it appears to be related to a known bug in the sync/atomic package (more details in https://pkg.go.dev/sync/atomic#pkg-note-BUG).
Thanks for reporting anyway!
Hey!
Was looking for a go lib to handle worker pools (after attempting to make my own with limited success), found this lib and it looked very promising. Seemed to run fine locally (running on Mac OS), but when I built it for our production servers (Ubuntu 18), I encountered this
Unaligned 64-bit atomic operation
error whenever we try to submit a task to the pool.Have you encountered this before/am I just doing something wrong? Here is the code on my side:
Pool setup
and then submitting:
Getting error =
FetcherProcessQueueResult recover from panic=unaligned 64-bit atomic operation
Build the server like so:
and Go version:
Here's the stack trace:
Any idea what could be happening here? let me know if you need any other details. Thank you!
The text was updated successfully, but these errors were encountered: