-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix hang during init on Windows if WMI is unavailable #74
Conversation
This issue affected Windows Vista and newer. During the `init()` phase a WMI call was made to get the system boot time. If WMI wasn't fully up the call would hang which blocked the entire application from initializing.
@@ -82,7 +74,15 @@ func (self *ProcFDUsage) Get(pid int) error { | |||
func (self *Uptime) Get() error { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we don't have to worry about this being called concurrently?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we can't guarantee how the library will be used I would feel more comfortable if it was concurrency-safe. I will make a change.
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 Fixes elastic#4373
* Update gosigar to fix Windows service timeout Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 Fixes #4373
Fix hang during init on Windows if WMI is unavailable This issue affected Windows Vista and newer. During the `init()` phase a WMI call was made to get the system boot time. If WMI wasn't fully up the call would hang which blocked the entire application from initializing.
Fix hang during init on Windows if WMI is unavailable This issue affected Windows Vista and newer. During the `init()` phase a WMI call was made to get the system boot time. If WMI wasn't fully up the call would hang which blocked the entire application from initializing.
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76 Fixes elastic#4373
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76 Fixes elastic#4373
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76 Fixes #4373
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76 Fixes #4373
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76 Fixes elastic#4373
This issue affected Windows Vista and newer. During the
init()
phase a WMI call was made to get the system boot time. If WMI wasn't fully up the call would hang which blocked the entire application from initializing.