SqlDependency.Stop() called from SqlDependency.OnChange handler freezes

SqlDependency.Stop() called from SqlDependency.OnChange handler freezes by Oyster

Closed

as Won't Fix Help for as Won't Fix

Type:	Bug
ID:	314039
Opened:	12/1/2007 8:45:59 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

If I am calling SqlDependency.Stop() from inside SqlDependency.OnChange handler for the same DB then SqlDependency.Stop() call freezes forever and application starts consuming all the CPU time available.

Details (expand)

English

.NET Framework 2.0 Service Pack 1

Windows XP Professional

English

1. Download and unpack attached file SqlDependencyStopFreeze.zip - it contains test application and steps to reproduce in Readme.txt file.
2. Create DB (as described in Readme.txt in attached archive), build application and run it (according to the instructions).

SqlDependency.Stop() call freezes and application starts consuming 100% of the CPU time (on one-core CPU, on multi-core it will be something like 100/number_of_cores %).

SqlDependency.Stop() call shouldn't freeze.

File Name	Submitted By	Submitted On	File Size
SqlDependencyStopFreeze.zip (restricted)	Oyster	12/1/2007	-

Posted by Oyster on 2/2/2009 at 8:52 AM

Why won't you fix this issue? Give some description please because issue is really quite disturbing - I was hoping that it's fixed in .NET FW 3.5 but it obviously not.

Posted by Microsoft on 12/1/2007 at 10:11 PM

Thanks for your feedback.

We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.
These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team

Posted by Microsoft on 12/1/2007 at 10:04 PM

Thank you for your feedback. We are currently investigating. The investigation process normally takes 7-14 days. If this issue is urgent, please contact support directly (see http://support.microsoft.com).

If at any time your issue is closed unsatisfactorily, you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team

Posted by Oyster on 12/1/2007 at 9:33 AM

I have verified this issue on .NET Framework 2.0 SP1 - it's still reproducible on Service Pack 1.

I also want to notice that problem described by my colleague Dmytro Kryvko here - http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=639623&SiteID=1 - probably has the same reason - infinite cycle inside query notifications-related System.Data code which never stops execution (please see Readme.txt from attached archive for more details).