Quick find hangs when regex search is enabled and \b is entered - by uiae

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 836678 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 3/19/2014 5:10:18 AM
Access Restriction Public

Description

Open any solution, hit ctrl-f, clear the search field, toggle "Use regular expressions" on, enter \b
Sign in to post a comment.
Posted by Microsoft on 3/28/2014 at 5:56 PM
Hi @uiae

We have been unable to reproduce the issue that you describe in our labs and are resolving this issue as "Not Reproducible".

If you are able to provide more details, in particular:

1. A video (Expression Encoder is a free downloadable recorder that can help capture this) showing the problem in action
2. Further details of the project (if the issue only reproduces for a particular project rather than all VS projects including newly created ones), exact version of Visual Studio, any extensions you may be using

Please provide the details on this bug - we may be able to reproduce and assess the issue and re-open the bug.

Thanks

Visual Studio Editor Team
Posted by Microsoft on 3/25/2014 at 9:12 PM
Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information. If you require immediate assistance with this issue, please contact product support at http://support.microsoft.com/ph/1117.
Posted by Microsoft on 3/23/2014 at 9:22 PM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you to submit the additional information we requested. If we haven't heard back from you with the requested information in the next 3 days, we will go ahead and close the issue.
Posted by Microsoft on 3/19/2014 at 8:44 PM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.
    
It may help if you provide us with Bucket ID, a dump file.

Bucket ID:
1.    Open Event Viewer        
2.    Click on Windows Logs -> Application
3.    Search for a 1001 event that occurred soon after you encountered the crash
4.    The bucket ID should be available in the event details
(there may be multiple 1001 events for any given crash - only one will have the bucket ID)
Dump File and Callstack:
You can get detailed steps about how to get the dump file by Visual Studio at http://blogs.msdn.com/debugger/archive/2009/12/30/what-is-a-dump-and-how-do-i-create-one.aspx

************************************************************
Please zip the file and use "FeedbackID-836678" as prefix of the file name.

************************************************************
You can use the following workspace to upload the file:
https://sftus.one.microsoft.com/ChooseTransfer.aspx?key=9a14de1c-e3bd-4455-bc71-1c5b704f4690
Password is {AgwJ+MvTm

We look forward to hearing from you with this information. If you require immediate assistance with this issue, please contact product support at http://support.microsoft.com/ph/1117.
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 3/19/2014 at 5:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If you require immediate assistance with this issue, please contact product support at http://support.microsoft.com/ph/1117.