ugly "pthread_create failed: Resource temporarily unavailable" running snaps
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
golang-1.6 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Michael Hudson-Doyle | ||
Yakkety |
Won't Fix
|
Undecided
|
Michael Hudson-Doyle | ||
golang-1.7 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
[Impact]
As reported here: https:/
Luckily for us, the bug was fixed upstream in the 1.8 release (https:/
It also turns out to be necessary to include two more upstream patches that fix test suite failures with new tzdata packages.
[Test case]
Run this code:
package main
//
import "C"
import (
"syscall"
)
func main() {
syscall.
}
a few thousand times and check for messages (it prints a message ~2% of the time or so without the fix).
[Regression potential]
The patch is simple, if a bit verbose (it has some per-architecture changes). It has not been the cause of any bug reports in 1.8 as far as I am aware. So I would characterise the regression potential as very low.
The tzdata patches are similarly well exercised as they are backports, and are necessary or the build will fail!
Changed in golang-1.6 (Ubuntu Xenial): | |
assignee: | nobody → Michael Hudson-Doyle (mwhudson) |
Changed in golang-1.6 (Ubuntu Yakkety): | |
assignee: | nobody → Michael Hudson-Doyle (mwhudson) |
no longer affects: | golang-1.7 (Ubuntu Yakkety) |
no longer affects: | golang-1.7 (Ubuntu Xenial) |
Changed in golang-1.6 (Ubuntu): | |
status: | New → Invalid |
description: | updated |
Changed in golang-1.6 (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in golang-1.6 (Ubuntu Yakkety): | |
status: | New → In Progress |
Changed in golang-1.6 (Ubuntu Yakkety): | |
status: | Fix Committed → Won't Fix |
It's a rather big change for a non-functional issue - by big I mean this change *could* potentially affect all the places where pthread_create was normally called. But seeing that the change had some testing time already and considering how this affects the snappy user experience, I'll be accepting the packages to the stable releases.