mirror of
https://github.com/weaveworks/scope.git
synced 2026-05-17 06:37:22 +00:00
If we run `getInitialState()` async there is some chance we will see another ebpf failure and call `useProcfs()` before `getInitialState()` gets to the last line, whereupon it will crash on nil pointer. Also it seems pointless to call `performEbpfTrack()` without waiting for something to feed in, so I suspect this is what the original author had in mind. It will slow down this one `Report()` on machines with a lot of processes or connections, but ebpfTracker restart is supposed to be a rare event.