Concourse-web crashes with 'concurrent map writes'

Hi all,

Has anybody seen / experienced an issue whereby concourse-web crashes with the following fatal error?

{"timestamp":"2019-11-18T07:37:17.285988274Z","level":"error","source":"atc","message":"atc.tracker.track.task-step.decrease-active-tasks.failed-to-decrease-active-tasks","data":{"build":9,"error":"pq: new row for relation \"workers\" violates check constraint \"workers_active_tasks_check\"","job":"branch-preview","job-id":9,"pipeline":"dev-tenantbe","session":"19.1.11.15","step-name":"helm unittest chart"}}
fatal error: concurrent map writes
fatal error: concurrent map writes
fatal error: concurrent map writes

goroutine 19154 [running]:
runtime.throw(0x1f3af1a, 0x15)
        /usr/local/go/src/runtime/panic.go:774 +0x72 fp=0xc001d7c180 sp=0xc001d7c150 pc=0x446c32
runtime.mapassign_faststr(0x1c35460, 0xc0017f1ef0, 0xc000e95140, 0x19, 0xc001d2a1b8)
        /usr/local/go/src/runtime/map_faststr.go:211 +0x417 fp=0xc001d7c1e8 sp=0xc001d7c180 pc=0x42ab37
github.com/concourse/concourse/vars.credVarsT

This is Concourse 5.7.0 running in a Kubernetes cluster, with 4 workers (2 VCPU, 2GB RAM) and 1 web node (2 VCPU, 2GB RAM)

Cheers!
D

It looks like you’re using the limit-active-tasks placement strategy. Is this correct?

I think you should post this as an issue in the github repo. Looks like a bug with that placement strategy: https://github.com/concourse/concourse/issues