← Back to issue list

the gox classic snap gets stuck consuming a lot of cpu

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1673186
Type
issue
State
open
Author
~zyga
Labels
classic isv
Created
Updated
Closed
—

Current evaluation

Classic snap wrappers could resolve their own /snap/bin launcher and spin in an exec/fork loop. Snapcraft later added a classic-PATH workaround in #2889, resolving the report.

Suggested action: close resolved

Reason: Git history contains commit 343ac2862, "meta: always generate snapcraft-runner to workaround classic PATH bug" from snapcraft#2889, directly addressing the diagnosed recursion. The report also provides a deterministic reproducer, the generated wrapper, and a working upstream workaround using bin/gox.

Evaluated by: mr-cal-bot

Impact: 58 Quick Win: 28 Complexity: 48 Confidence: 92 Actionability: 92

Issue body

I'm trying to make a snap for gox: https://github.com/mitchellh/gox It needs to call the go binary installed in the system, so I made it classic. Attached is the yaml to make the snap. Build it with snapcraft, install it with --classic and: $ taskset 2 gox -h (taskset to avoid the bug with multiple cores that Chipaca is investigating.) It just gets stuck there consuming CPU, check with top.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 58
Quick Win: 28
Complexity: 48
Confidence: 92
Actionability: 92
close resolved Classic snap wrappers could resolve their own /snap/bin launcher and spin in an exec/fork loop. Snapcraft later added a classic-PATH workaround in #2889, resolving the report.
stealth/space-bunny-alpha
Impact: 58
Quick Win: 31
Complexity: 42
Confidence: 96
Actionability: 93
close resolved Resolved: classic snap wrappers could recursively resolve unqualified commands through /snap/bin and spin the CPU. Snapcraft later added opt-out and automatic PATH handling.
qwen/qwen3.6-35b-a3b
Impact: 5
Quick Win: 1
Complexity: 20
Confidence: 70
Actionability: 30
close not a bug User reports gox classic snap hangs consuming CPU when running gox -h. Support question about third-party tool packaging, no maintainer response in 3479 days.
qwen/qwen3.8-27b
Impact: 20
Quick Win: 8
Staleness: 95
Complexity: 60
Confidence: 65
Support Request: 10
close stale 2016 report that a classic-confinement snap of gox hangs at startup consuming high CPU, worked around with taskset due to a separate multi-core bug. No maintainer activity in ~9 years; the referenced multi-core bug is long since fixed.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 45
Confidence: 90
Support Request: 20
close stale Classic snap for gox hangs and consumes high CPU during execution. No maintainer comments or activity for nearly a decade.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 15
Confidence: 90
Support Request: 65
close stale Classic snap for gox hangs and consumes high CPU when invoked. Open for ~9 years with no maintainer response or comments.
qwen3.6-35b-a3b-mtp-q6
Staleness: 99
Complexity: 15
Confidence: 95
Support Request: 70
close stale Classic snap for the gox tool hangs and consumes high CPU on startup. Open for nearly 9 years with zero maintainer comments or activity.

Update history

Date Change
created

Related work

  • Related To: gox#89 (confidence 98%)

    Upstream change proposed in the discussion makes the snap command explicitly use bin/gox, avoiding recursive PATH resolution.

  • Likely Fixed By: snapcraft#2889 (confidence 94%)

    Implemented in commit 343ac2862 by generating snapcraft-runner specifically to work around the classic PATH bug.

Related issues

No related issues found above the similarity threshold.