Page 1 of 1
VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Fri 21 Aug 2015 01:49
by israeld
We have a solution working flawlessly in VS2013, using dotConnect for Oracle (8.5) running against 64bit Oracle Client (11.2.0).
When opening the solution to VS2015 the CPU usage hits the roof and flatlines. We are able to start debugging but unable to stop debugging (debugger won't detach), also when trying to close the IDE the devenv.exe process stays behind with CPU usage flatlined.
This is the exact same behaviour that this person is reporting (although they do not appear to be using dotConnect):
https://social.msdn.microsoft.com/Forum ... diogeneral
I should point out that if I comment out all of our connection strings from our web.config files these problems do not occur. Likewise if I switch our connection strings over to direct=true the problems do not occur.
Any help would be greatly appreciated?
Re: VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Tue 25 Aug 2015 15:40
by Pinturiccio
We could not reproduce the issue. Please create and
send us a small test project which reproduces the issue. Please also describe the steps we should perform for reproducing the issue.
Re: VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Mon 31 Aug 2015 03:10
by israeld
Here is a very simple example, just an empty web project containing a web.config with sanitised versions of our connection strings. Using this example we have replicated the issue on 3 different developers machines.
Here are the steps to replicate the issue:
- Open the solution
- CPU usage should now climb up for the devenv process and not return to zero
- Close Visual Studio
- The devenv process should now to stuck, chewing up CPU, unable to close until the process is killed manually.
Apologies for the file host, I couldn't figure out how to add an attachment to this post:
http://s000.tinyupload.com/?file_id=141 ... 1752175663
FYI we are running:
- Windows 8.1
- VS2015
- x64 Oracle Client 11.2.0.1.0
- dotConnect 8.5
Re: VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Fri 04 Sep 2015 13:21
by Pinturiccio
Thank you for the additional information. We are processing your request. We will contact you as soon as possible.
Re: VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Tue 08 Sep 2015 19:00
by gmilczarek
Hello,
I encountered the same error using VS2015 and dotConnect 8.5,
but direct connection dont solve it.
Re: VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Tue 08 Sep 2015 21:41
by israeld
Yes you're right, direct didn't solve the problem for us either. I thought it did when I made my first post but that was a mistake.
Hopefully the devart folks can come through with a fix for us, this is the only thing stopping my team from moving to VS2015.
Re: VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Mon 14 Sep 2015 13:54
by Pinturiccio
Unfortunately, there is an invalid project by this link. We have created an empty Web Application and added your web.config to it, but we can't reproduce the issue.
Please send us the complete test project, which reproduces the issue. You can send us this project using the following
form. At the bottom of this form you can attach a file up to 2 MB.
Please also tell us the edition of your Visual Studio.
Re: VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Tue 15 Sep 2015 00:12
by israeld
I have submitted a new example solution through the contact form.
Re: VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Fri 18 Sep 2015 11:37
by Pinturiccio
We have reproduced the issue. We will investigate it and post here about the results as soon as possible.
Re: VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Sun 18 Oct 2015 23:40
by israeld
Hi Pinturiccio,
Has there been any progress on this issue?
Re: VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Fri 23 Oct 2015 13:07
by Pinturiccio
We are investigating the issue and will post here when we get any results.
Re: VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Tue 27 Oct 2015 11:25
by Pinturiccio
When studying the issue, we have found that it is reproduced not only with dotConnect for Oracle, but with other providers too, even with providers to databases other than Oracle.
Visual Studio 2015 has a new feature of adding connection strings from the web.config file to Server Explorer automatically. It seems that it has a bug causing Visual Studio to stop responding when there are 5 or more connections in the web.config file.
Since this is a Visual Studio bug, we cannot do anything with it. We recommend you to contact Microsoft support.
Re: VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Wed 04 Nov 2015 04:30
by israeld
Pinturiccio wrote:
Since this is a Visual Studio bug, we cannot do anything with it. We recommend you to contact Microsoft support.
I'm sorry but that's not a good enough response.
As stated on your
About Us page, Devart is a
Microsoft Silver Application Development Partner, as a partner organisation you should be able to contact Microsoft directly. Furthermore I think that you owe it to your paying customers to do so.
You also advertise that the product has VS2015 support
https://www.devart.com/dotconnect/oracl ... patibility and right now you are not providing that compatibility. How can you claim VS2015 support when it doesn't actually work?
My organisation has been a loyal Devart customer for several years and have been extremely happy up until now. Right now we are stuck, unable to upgrade to VS2015 and it is not fair for you to push it back on me and tell me to contact MS.
Re: VS2015 - CPU usage flatlined, unable to detach debugger or close IDE
Posted: Fri 06 Nov 2015 14:55
by Pinturiccio
We have submitted a ticket to Microsoft support:
https://connect.microsoft.com/VisualStu ... s/1987980/
We will post here when Microsoft's support team replies to it.