The 14 June 2024 build (13529) is out.

[Elena]

Hi, I hope this message will be noticed. I did not open a new topic because it is definitely related to build 13529 and over.

I also have experienced major slowdowns since b13529.
What I wanted to point out is that the culprit was indeed Browse Tracker, I disabled it and now everything is fine as before.
At the moment of writing this, current NB is 13600 and the problem is *still present*. Therefore, I simply have to keep the plugin disabled. Hope this helps.
Therefore, please consider fixing the plugin, which is causing major slowdowns since b13529

Thx

[Miguel Gimenez]

This post describes a problem with the same commit producing the delays.

@Pecan, can you take a look?

[Pecan]

This post describes a problem with the same commit producing the delays.

@Pecan, can you take a look?

I'll have a look today and try to reproduce it.

[Pecan]

Hi, I hope this message will be noticed. I did not open a new topic because it is definitely related to build 13529 and over.

I also have experienced major slowdowns since b13529.
What I wanted to point out is that the culprit was indeed Browse Tracker, I disabled it and now everything is fine as before.
At the moment of writing this, current NB is 13600 and the problem is *still present*. Therefore, I simply have to keep the plugin disabled. Hope this helps.
Therefore, please consider fixing the plugin, which is causing major slowdowns since b13529

Thx

@Elena: I apologize for missing your post.
I've reworked the Editor hook for efficiency such that only flags are set in that code and moved all processing of BrowseTracker arrays to the idle processing time routine.

Please consider retesting, since I was unable to recreate the slowdown and let us know the outcome.

CodeBlocks revision 13606.

Regards, pecan

[Pecan]

This post describes a problem with the same commit producing the delays.

@Pecan, can you take a look?

I was unable to recreate the described assert and slowdown in the BrowseTracer plugin. But I've done some extensive re-coding to elimate any array processing in the editor hook and moved that processing to OnIdle().

I've also added more guards to avoid out-of-bounds conditions in the AddEditor() routine.

CB commit13606

[Pecan]

Hi, I hope this message will be noticed. I did not open a new topic because it is definitely related to build 13529 and over.

I also have experienced major slowdowns since b13529.
What I wanted to point out is that the culprit was indeed Browse Tracker, I disabled it and now everything is fine as before.
At the moment of writing this, current NB is 13600 and the problem is *still present*. Therefore, I simply have to keep the plugin disabled. Hope this helps.
Therefore, please consider fixing the plugin, which is causing major slowdowns since b13529

Thx

Fixed svn 13612.

The actual slowdown culprit was CodeCompletion  (CC) "Parse while typing" setting. However when the user disabled settings while a project was loaded, CC clobbered the settings back to the older condition as the project was closed.

Although the fix preserves the users settings in the .conf (global settings) the user will still have to re-parse the projects/files in order to apply the changed CodeCompletion global settings to the projects or files.

The easiest way to do that is to close and reopen the workspace or right-click on a project in the workspace tree and select 'Reparse this project'.

[Elena]

Hi, thanks for your support. Since at present I am not equipped to compile C::B I will surely test once the new NB binary is ready (it seems there haven't been any new NB since December btw)

[Miguel Gimenez]

The text in Parser::ShowGlobalChangeAnnoyingMsg() should allow translation, something like this:

Code Select Expand


warningMsg = _("The global settings change does not take effect\n"
               "until the projects are either reloaded or reparsed.\n\n"
               "You can selectively reparse projects by right clicking\n"
               "on the project title in the Workspace tree and selecting\n"
               "'Reparse current project'.");


[ollydbg]

The text in Parser::ShowGlobalChangeAnnoyingMsg() should allow translation, something like this:

Code Select Expand


warningMsg = _("The global settings change does not take effect\n"
               "until the projects are either reloaded or reparsed.\n\n"
               "You can selectively reparse projects by right clicking\n"
               "on the project title in the Workspace tree and selecting\n"
               "'Reparse current project'.");


I have fixed that in the SVN now, thanks.