MMX for Delphi 10.3 Rio

[Uwe Raabe 2059]

6 hours ago, Jacek Laskowski said:

I am still using MMX version 15 and waiting for a fix.

As these problems are hard to track down, I need to dedicate some time to that fix. Unfortunately I am not able to spend a significant amount of time on MMX in the moment, so it may take a while for the V15 beta to proceed.

[Jacek Laskowski 57]

On 10/4/2019 at 6:09 PM, Uwe Raabe said:

As these problems are hard to track down, I need to dedicate some time to that fix. Unfortunately I am not able to spend a significant amount of time on MMX in the moment, so it may take a while for the V15 beta to proceed.

I'm not sure it's a good lead, but I have an observation related to the MMX suspension.
If just before ctrl+E (entity edition) I press ctrl+S (save changes in files) I have no suspension, and every time MMX suspends Delphi I forget to press ctrl+S.

This may be some kind of key 😉

[Uwe Raabe 2059]

Thanks, will check that.

 

Btw, I have also seen this issue from time to time and TaskManager indicates some threads waiting for I/O completion. So that may indeed be related.

[Carlos Tré 9]

On 10/8/2019 at 9:52 AM, Jacek Laskowski said:

I'm not sure it's a good lead, but I have an observation related to the MMX suspension.
If just before ctrl+E (entity edition) I press ctrl+S (save changes in files) I have no suspension, and every time MMX suspends Delphi I forget to press ctrl+S.

This may be some kind of key 😉

I used to have the same problem, but it seems to have gone away after I uninstalled Mitov run time, which I did to solve a problem I was having with TListView in FMX projects - it rendered that component unusable, crashing Delphi IDE every single time I tried.

 

-- Carlos

 

[Jacek Laskowski 57]

I don't use Mitov Library. I don't use any libraries working in design time, only a few experts: CnPack, GExpert, DocumentationInsight, Code Insight Plus and RFindUnit.

[Jacek Laskowski 57]

However, saving an entity before editing does not always help, MMX rarely hangs, but it still happens.
But I have new observation. If I manually add new property to the class, but without the getter and setter (as in the picture) and press the ctrl+E shortcut, first the question appears about adding accessor methods and only after clicking "Yes" MMX hangs.

 

Edited October 24, 2019 by Jacek Laskowski

[Jacek Laskowski 57]

@Uwe Raabe

Some time ago I discovered that GExperts in "Uses Clause Manager" module has a parser that works in the background and creates files from the cache on the disk. Previously I suspected that MMX suspensions occur when accessing source files, so I thought GExperts might interfere with MMX somehow. I completely disabled "Uses Clause Manager" and since then the number of IDE suspensions when using MMX has dropped dramatically. It still happens, but this is maybe 10% of the previous state.

I hope this helps a little bit.

 

[Uwe Raabe 2059]

2 minutes ago, Jacek Laskowski said:

has a parser that works in the background

That's basically what MMX does, too. Besides the IDE itself (with active CodeInsight) there may as well be other plugins spawning their own parser process. This bothers me for years now. It might get better when LSP is up and working reliably, but that might take a while and will be restricted on newer Delphi versions.

 

Thanks for the tip, though. 👍

[Uwe Raabe 2059]

I finally got hit by the problem myself and did some deeper investigation. It turned out that the freeze happens when System.pas was parsed in the background. It contains some constructs with conditional defines that are not handled well by the internal parser. Adding System to the list of excluded files avoids that.

 

Then I made a complete scan over the available Delphi source files (at least those present on my development machine - alas, some platforms are missing) and found two other source files with the same problem: IdThreadSafe.pas and IdGlobal.pas.

 

It would be great if those people affected by this problem can test this workaround and add System, IdGlobal and IdThreadSafe to the Excluded list. 

[Jacek Laskowski 57]

Yuuppii! 🙂

I will try this workaround and test behaviour, thanks for effort and for support MMX!

 

From the more complicated code I use Spring4D, FireDAC and mORMot, did you check them?

[Uwe Raabe 2059]

Unfortunately the problem is still present. The good thing is, that I now have the environment to investigate it. May take some time though...

[Jacek Laskowski 57]

Yes, despite the exclusion of the pointed modules, I have the IDE suspension

 

 

But it is worth adding that I have a suspension after I modify the interface method and then I try to edit (ctrl+E) the method in the class that corresponds to the modified interface method.

This is probably the only (certainly the main >90%) case of suspension.

Edited February 24, 2020 by Jacek Laskowski

[Uwe Raabe 2059]

There is a new beta release 15.0.8.2366 available. Besides some smaller fixes it has an option to produce some CodeSite log files to track down these freezing issues. Logging can be activated in the registry. For convenience I have attached a reg file that creates the necessary entries, but doesn't activate them:

Quote

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Raabe Software\MMX\15.0\Debug]
"CSUseLogViewer"=dword:00000000
"CSUseLogFile"=dword:00000000

If the CSUseLogFile entry is set to 1, MMX creates a log file for each Delphi start in <My Documents>\My CodeSite Files\Logs with file name MMXLog_<timesptamp>.csl. When you encounter that freezing issue or performance drop while logging is active, just send me the corresponding log file.

MMXDebug.reg

[ULIK 16]

Uwe,

 

having just installed this new beta, I failed to get CodeSite Logs running. I installed MMX as 'Just for me' and applied the registry change: I have set both loggers to '1' and started the IDE and tried to create such a log. But until now, nothing has been written to My CodeSite Files\Logs nor to my CodeSite Live Viewer. Is there a way to check if logging is active? At the moment my test steps were: creating a new VCL app, then added a new property by MMX Editor. Should this write some log entries? I also checked my CodeSite dispatcher log and can't see any entries.

 

 

[Jacek Laskowski 57]

I don't make any logs either. I don't have a CodeSite installed, is it necessary?

[Uwe Raabe 2059]

OK, will have a look...

[Uwe Raabe 2059]

Damn, the build server intentionally removes the USE_CODESITE define for the Release, probably to avoid that slipping through.

 

There is V15.0.9.2368 that should behave better.

45 minutes ago, Jacek Laskowski said:

I don't have a CodeSite installed, is it necessary?

You don't need a complete CodeSite installation. I added a separate download for CodeSite Tools which are necessary if no CodeSite is installed.

 

If anyone has doubts installing CodeSite Tools - just don't do it. You cannot have those logs then.

[Jacek Laskowski 57]

Yes, now logs working! I wait for freeze 😉

[ULIK 16]

Great, now I get the logs. I enabled 'Check Packages' on 'General' settings again and tested it again:

- starting the IDE

- creating a new VCL App

- adding a new property

 

Still that long delay on first loading.  See attached log file.

MMX_Commented.csl

[Uwe Raabe 2059]

@ULIK More than 16 seconds spent in LoadAvailableInterfaces. Does that roughly match the delay you see?

[ULIK 16]

Yes, opening the dialog the very first time requires about 13-16 seconds, also without CodeSite logging enabled.

[Uwe Raabe 2059]

That is a pretty long time for a rarely used feature (a property implementing an interface). I will see what can be done better here.

[ULIK 16]

No sure that I understand you right: adding a new property to a class is not so much uncommon for me (and that's what I did: selecting the new TForm1 object and added a property. Or do you mean that there is MMX internal code doing some strange things?

[Uwe Raabe 2059]

LoadAvailableInterfaces populates the Implements combobox at the bottom right of the property dialog. Using a property as the implementor of an interface is not that common.

[ULIK 16]

Thanks for explaining!