Looking at the dbgsrv command line, I see nothing obviously invalid. It does contain `-p ### -tid ###` (prolly process/thread id). Could it be this process/thread is killed before dbgsrv has had a chance to attach?
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
yep, saw it often. from what I recall
@j00sean suggested killing RuntimeBroker a few times. -
Thanks. The latest BugId is already killing dbgsrv and BrowserBroker, so that does not appear to solve the problem. I can manually work around it by restarting BugId but I'd rather be able to detect it (so BugId can do this automatically) or better yet avoid it altogether.
-
This bug causes my Fuzz Framework to idle while it's waiting for Edge to load a webpage, which will never happen. It will restart Edge after a timeout, but it's just wasting time until that happens.
End of conversation
New conversation -
-
-
yup I encountered this bug too.. There is an issue related to this problem in your github,but it didn't solve this. I give up using Bugid as a crash monitor when fuzzing Edge
-
How do you detect them now then?
End of conversation
New conversation -
-
-
Has been an issue for a while. I don't think there is a solution for it yet, only workarounds.
-
Do you happen to have a better workaround?
-
I have started using webview to fuzz Edge. Much lighter and the dbgsrv error appears at a reduced frequency.
-
Best solution by the moment. Use webbrowser (IE) and webview (Edge) controls
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.