MathewV

We narrowed it down to when there is a huge unit open (over 5000 lines of code). If that is closed in the IDE then it works. We have reported it https://quality.embarcadero.com/browse/RSP-32942 It is not the Search that is the issue but the search menu. I got around this issue by adding a search button to the tool bar Right-Click and select customize Then go to the search group and drag "Find in Files" into your tool bar. Hope that helps

It is maddening as I have not had it happen again. We first saw the issue in D11 but never persevered because of the issues with debugging DLLs when using packages (fixed in D11.1 although break on exceptions never make it to code). Darren, how long have you used D11.1? Was it in a project that you opened for the first time? The fact that I have not been able to repeat it makes me think that perhaps there was some sort of indexing going on and that is now complete????? John, I read elsewhere that some are having issues with the Refactor menu too. I've not see that myself.

Just tried it again 20 times and could not make it happen!!! Earlier today it happened every single time I had highlighted text and clicked the Search menu. We have three devs and 3 installs. While I was getting it occasionally at the start one other install had it all the time. Then I started getting it all the time. The third only got the issue occasionally. It's a 5 million line project will all units ANSI. I'll keep an eye on it and see if there is something else that we can spot.

Hi All, Anyone else having this issue? When I click on the Search Menu the whole IDE locks up for 5 seconds and then crashes to Desktop. (Win 11). I have narrowed it down that it only happens when I have some text in a pas file highlighted. If i click elsewhere in the pas file to deactivate the highlight then I can access the search menu. Many years of copying highlight text and searching for it will be a hard habit to break so hoping someone may have a clue about this one. I added notes to a QA issue [RSP-32942] Thanks Mathew

Very happy to say that it all works in D11.1 - we can finally move from D10.2 and it's frustrating compiler errors. I love Delphi but I still feel that their communication with us on issues like this is appalling. They should welcome engagement from their users. We all want Delphi to be the best development platform in the world so we can get on with our work and they have an even better product. I feel that as a user of Delphi for over 26 years counts for nothing with them and I write this in the hope that someone internal sees it and it sparks an internal discussion on how they engage with us.

Awesome. Thanks for that.

Seems to have worked - thanks for that.

@Uwe Raabe this is great - thanks so much for putting it together. One question. We recently shifted our project to FMX but updated the units by removing "VCL" from the project Scope Names and adding "FMX". When we ran this cleaner it is inserting VCL where we need it to be FMX. Aside from a manual review, is there a known solution for this? Thanks again Mathew

Yes, I'm hoping that someone with some influence will be able to raise this with them. With the new focus on "Win32" dev by Microsoft, this is in Delphi's interest to work with us all on getting this right. We're all developers, we know what it is like to debug strange issues. It is that they ignore these issues while pushing new features that frustrates me. Thanks for the suggestions. It is set "correctly" to my understanding and has never been an issue in all Delphi versions before 10.2 (granted that we changed our 5 million line project to 64bit in 10.2 so before that it was 32bit). The sample program I used in the video is unchanged between 10.2 and 11. My hope would be that if I could debug in 10.2 then I should be able to in 11 without needing to change settings. Personally, I think it's time that they made Delphi a 64-bit program, written in Delphi! I remember in Delphi 1 Borland marketed that they wrote Delphi in Delphi (chicken and the egg comes to mind). I wish they would do the same now and then they would see what we are dealing with. Still, the small sample app shows this issue so well, I just wish they would engage with us on this so that we can use D11 and Delphi keeps getting better.

Is anyone else having issues where you step into a DLL function and all you get is the CPU screen? There are so many reasons why we want to move our 25 year Delphi project to D11, but this one is stopping us and there has been no traffic on the RSP that has been added (https://quality.embarcadero.com/browse/RSP-35879) I recorded a video here https://www.screencast.com/t/qEOV7MO00Jq and you can download the OP's sample project from the RSP. If this is a user/setting error, please let me know!

Did you find a solution to this? We have a similar issue and can not move to D11 at this point. There is no response to the issue that we added to on this. https://quality.embarcadero.com/browse/RSP-35879