This repository has been archived by the owner on Jul 31, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 327
Goroutine started on init() function #1074
Labels
Comments
Found this goroutine running during my tests today. This strikes me as extremely bad practice to start unwanted goroutines no matter how "cheap" they are. If the package requires a Goroutine to run, starting it should be part of the public API that users have to start themselves. |
Likewise importing these google APIs will also start the mystery go routine
|
I can't explain how, but I believe this goroutine has a serious bug causing the CPU to spin, and somehow blocking program start. Reported in: #1200 |
agreed this should not be happening. i had to investigate wtf the library was and whether it posed a security risk to my application. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
In this init() function a gorouting is fired.
This looks like an strange behaviour for a lib, because any program importing this lib will have your goroutine running.
Found looking for a problem in Telegraf: influxdata/telegraf#5612
The text was updated successfully, but these errors were encountered: