Getting Visual Studio Error on debugging "a 64-bit debugging operation is taking longer than expected."

user_8918560 0
Viewed 6318

I am getting this error on debugging Visual Studio 2017 with platform target as 64 bit. Tried many workarounds but nothing worked. Anybody has faced similar issue in the past and knows the workaround, please let me know. Nothing was changed in my machine, no patch, no update.

Tried below workarounds but nothing worked out.

Workaround 1: 1.Run cmd.exe as administrator 2.Type in and run the following commands:     netsh winsock reset catalog     netsh int ip reset reset.log hit

Workaround 2: Switch target platform from x64 to x86 Build project in x86 Switch back the target platform to x64.

Workaround 3: Reninstalled Visual Studio 2017 Professional

64 bit debugging error Above error is followed by below error on click of terminate button. Operation taking longer than expected error Above error is followed by below one Remote debugger closed error

visual-studio-2017
4 Answers

For somebody maybe still frustrated and struggle with this problem, I don't understand the detail about Visual Studio but I used this solution. I use VS Ultimate 2013 Version 12

1. Using code to exit running program

I found this, I assume that stop debugging leaves some process stuck and locked. Then I use this code to exit my running program

int c = cvWaitKey(1);
    if (c == 27 || c == 'q' || c == 'Q')
        break;

2. Terminate All

You can use this way when your program break. Just click break then Debug -> Terminate All https://i.imgur.com/2hYIJdu.jpeg

3. Close Visual Studio Debugger Monitor

When your program is already locked and the task manager can't end task not responding program windows you can use this way. Close Visual Studio -> Open task manager -> End task your stuck running program window -> find Visual Studio Remote Debugging Monitor -> end task

Sorry for my bad English, hope it can help you. CMIIW

user_109476190

Make sure you didn't set some option that uses external stuff.

In my case (C++, MFC) while debugging external code I set a checkmark to use "Microsoft Symbol Servers" (.pdb locations) an forgot about that. The result was that the following starts of debug sessions were incredibly slow (IDE was downloading a lot from MS servers) and I faced mentioned "longer than expected" message. I unchecked that option back via "Visual Studio 2017"->Tools->Options->Debugging->Symbols and it solved my case.

user_59352490

For me this was happening because script debugging was enabled and chrome was the default browser. Once I either turned off script debugging or switched to Edge everything worked fine.

user_6347690

Somehow I had a previous debug thread still running. I terminated it from the task manager, and everything went back to normal.

user_34115560
Related