Canonical Juju

  1. Bug #1833155
  2. Comment #2

Comment 2 for bug 1833155

Revision history for this message
Joel Sing (jsing) wrote : Re: GCE access failures resulting in memory leak

On the Juju controller in question:

$ for i in {1..10}; do juju_heap_profile | grep '# Stack = '; sleep 120; done
Querying @jujud-machine-1 introspection socket: /debug/pprof/heap?debug=1
# Stack = 1344143360 / 1344143360
Querying @jujud-machine-1 introspection socket: /debug/pprof/heap?debug=1
# Stack = 1344274432 / 1344274432
Querying @jujud-machine-1 introspection socket: /debug/pprof/heap?debug=1
# Stack = 1347649536 / 1347649536
Querying @jujud-machine-1 introspection socket: /debug/pprof/heap?debug=1
# Stack = 1351712768 / 1351712768
Querying @jujud-machine-1 introspection socket: /debug/pprof/heap?debug=1
# Stack = 1353416704 / 1353416704
Querying @jujud-machine-1 introspection socket: /debug/pprof/heap?debug=1
# Stack = 1357807616 / 1357807616
Querying @jujud-machine-1 introspection socket: /debug/pprof/heap?debug=1
# Stack = 1358757888 / 1358757888
Querying @jujud-machine-1 introspection socket: /debug/pprof/heap?debug=1
# Stack = 1363542016 / 1363542016
Querying @jujud-machine-1 introspection socket: /debug/pprof/heap?debug=1
# Stack = 1368031232 / 1368031232
Querying @jujud-machine-1 introspection socket: /debug/pprof/heap?debug=1
# Stack = 1370947584 / 1370947584