>be a developer for a company developing enterprise software for windows >we install a windows service on each machine of the customer >a commit introduces bug that causes stack overflow on the service >try to debug it >service crashes on start but its process remains running >try to kill it via services >it doesn't die >try to kill it via task manager >nope "access denied" >wtf? I'm admin on my system >try to kill it with process hacker with admin rights >nope! process refuses to die >try to attach visual studio debugger on it >debugger crashes with error "CATASTROPHIC FAILURE" >the only way to get rid of it was to restart the computer >pretty much every service that crashes on start with stack overflow becomes immortal
and another one
>have a ticket to research something on our windows service >good chance to try stuff I want >try to exploit the clusterfuck of security the windows has >modify the service to scan all the computer for processes that belong to other users >once it finds one, it takes it's token and spawns another process with that token >this process was made by me to use the users token to access stuff from my computer >lure a colleague to log on my computer to test it >tell him to open a program >trap was triggered >the process was supposed to copy all of his private files on NAS to my computer >it fucking worked >called development and IT leader to show that >I'll never forget the look on IT leader's face
I'm unironically phoneposting and it loads, whats your browser?
Brandon Mitchell
furfax
Logan Long
OP is a twat
Caleb Allen
I ran into something like the first about three months back, but it was caused by a bad Windows Server patch. We rolled stuff back, and it was fixed with the next month's updates.
Was incredibly stupid and a huge waste of time to debug, though.
A single service has a hiccup and your brilliant idea is to sink the entire wangblows service process with all hands. Fedora is perfect for you stick with it.
windows services call the OnStart method right? if the OnStart takes too long to return it times out but if you spawn a thread in OnStart, it returns but the thread is still alive the service will timeout but keep running in the background
my guess is you are running something async in OnStart that is bound to a system library, maybe for networking or disk i/o
you need to keep a reference in your service class and close any threads in OnStop
Logan Russell
oh and also dont kill services.exe u mong, find your actual service in the processes tab
Robert Reyes
also while im here if you want to debug it add a Thread.Sleep(10000); in the constructor start the service and you have 10 seconds to attach the debugger if you dont get any exceptions thrown open the exception settings window and tick CLR also check windows logs for errors if you really fucked up just convert it to a console application and start from there
Chase Miller
>try to kill it via task manager >nope "access denied" >wtf? I'm admin on my system Tell me your company name - because if they have devs like you, I want to be absolutely sure we never have anything to do with you.
Brayden Murphy
>Jow Forumstoddlers insist on browsing the internet exclusively riced out 5UP3R H4XX0R no bloat thinkpads >Jow Forumstoddlers shit on phoneposters and "touchjizz bloat" whatever the hell that is >Jow Forumstoddlers are literally unable to view videos on the internet very interesting turn of events
