71
General (but related to Code::Blocks) / Re: Generate a file '*_linux.cbp' to '*_win.cbp' or vice versa
« Last post by Miguel Gimenez on April 22, 2026, 11:44:29 am »Profile spammer olenna reported to moderator.
News:
The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .
Recent Posts
72
Help / Re: Cannot find the compiler
« Last post by thereforerepair on April 22, 2026, 10:17:41 am »Go to Settings -> Compiler, select the "Toolchain executables" tab and fill the controls with your compiler's location (use where gcc.exe in the cmd prompt) and program's names.
Great! The instructions shared are accurate. Executing the correct command is crucial to ensuring the program works and runs.
73
Help / Re: Code editor window closing after saving files (related to very large projects)
« Last post by Pecan on April 19, 2026, 08:19:18 pm »I have run CB 20.05 in vmware with a memory size of 4gig and was unable to get the file closes on save that Stratelier gets.
I did experience the memory thrashing during a file save when memory usage reached 91%.
I ran CB under the debugger and chased high memory usage happening when scintilla double buffered the file. There was sometimes a near 10 second pause of the whole system.
Most likely memory thrashing.
I was unable to determine how files were closed when they were saved ok.
If they were not saved ok, we should have seen the message from this function:
I can only guess that this is some kind of physical memory error or that the stack got corrupted and the code returned to the wrong place.
I can find no code that saves the files ok and then closes them.
I did experience the memory thrashing during a file save when memory usage reached 91%.
I ran CB under the debugger and chased high memory usage happening when scintilla double buffered the file. There was sometimes a near 10 second pause of the whole system.
Most likely memory thrashing.
I was unable to determine how files were closed when they were saved ok.
If they were not saved ok, we should have seen the message from this function:
Code
if (!cbSaveToFile(m_Filename, m_pControl->GetText(), GetEncoding(), GetUseBom(), robustSave))
{
wxString msg;
msg.Printf(_("File %s could not be saved..."), GetFilename().c_str());
cbMessageBox(msg, _("Error saving file"), wxICON_ERROR);
return false; // failed; file is read-only?
}
I can only guess that this is some kind of physical memory error or that the stack got corrupted and the code returned to the wrong place.
I can find no code that saves the files ok and then closes them.
74
Help / Re: Why does the code editor window close after saving a file?
« Last post by Stratelier on April 19, 2026, 01:17:25 am »Sorry. At the time I was following the instructions from developer.gimp.org (and there are quite a few more for Windows than on Linux), one of which is to fetch it via git command-line.
The issue does seem specifically related to very large projects, as I cannot reproduce it in isolated files or "hello world" sized projects.
As for my system: A laptop from 2014 with 4GB shared RAM. It has room for 8 to 16GB but the RAM sockets are the last thing in the teardown (ugh). So it tends to be under a bit of stress.
The issue does seem specifically related to very large projects, as I cannot reproduce it in isolated files or "hello world" sized projects.
As for my system: A laptop from 2014 with 4GB shared RAM. It has room for 8 to 16GB but the RAM sockets are the last thing in the teardown (ugh). So it tends to be under a bit of stress.
75
Help / Re: Why does the code editor window close after saving a file?
« Last post by Pecan on April 19, 2026, 01:06:31 am »@Statelier
I was asking about where to download the Gimp source that's shown in the project window.
But I finally found it (I think). Downloaded it, made a project from it, and tried to get the problem as described. No luck though. It works ok for me. (Windows 11 64bit 32Meg memory).
Now I'll re-create cb 25.03 from source and see if I can step through "save" in the debugger with many files of Gimp loaded.
Please describe the hardware you're using. I'd like to use vmware to create a similar system and test your environment there.
I was asking about where to download the Gimp source that's shown in the project window.
But I finally found it (I think). Downloaded it, made a project from it, and tried to get the problem as described. No luck though. It works ok for me. (Windows 11 64bit 32Meg memory).
Now I'll re-create cb 25.03 from source and see if I can step through "save" in the debugger with many files of Gimp loaded.
Please describe the hardware you're using. I'd like to use vmware to create a similar system and test your environment there.
76
Help / Re: Why does the code editor window close after saving a file?
« Last post by Stratelier on April 19, 2026, 12:47:08 am »Where can I download the source causing the problem.
I want to re-create the problem while running CB under the debugger.
Also, are you sure that the Code Completion plugin is disabled?
That wait after saving feels like a timer pop then running some code.
Or a lock on the main gui code being released.
Very suspicious of a bug from last century.
Like I said, from the Sourceforge.net page linked from the Codeblocks Downloads page:
1 - https://www.codeblocks.org/downloads/binaries/#imagesoswindows48pnglogo-microsoft-windows
2 - links to -> https://sourceforge.net/projects/codeblocks/files/Binaries/25.03/Windows/codeblocks-25.03-setup.exe
For certainty, the SHA1 hash of the installer should be 99eafbb34f62cfaee58da6e0ae6e0b4ce88c9f1e (I downloaded a fresh copy from SF and it matches), though this does not match ANY of the signatures cited by the dappCDN downloads page (https://dappcdn.com/download/devtools/code-blocks?get=codeblocks-25.03-setup.exe).
If I download the equivalent installer from dappCDN, its SHA1 hash is accd7900ec89ec9bf1f45bc70dfd20dbb4a350f6 and this does match the signature cited on the page. I will try installing that one separately for comparison. (And in any case, the SHA1 of the main executable, codeblocks.exe, is the same either way: 7d16aadf9e10ab7fa39decedc6714bfcee5623f1)
And that is correct: I have ALL plug-ins disabled.
I would love to load one of GIMP's dependencies (like babl) just to have a second (smaller!) project as a datapoint, but for the moment I cannot actually create any new projects (no templates available), nor can I simply point CB at the source folder either.
Additionally, this all does not occur if I simply open a file directly (outside any project) and make/save changes. There is no strange lag after saving, the editor window stays open (as it should). And it is consistent between both installations.
In other words, this seems SPECIFICALLY correlated to the overall size of the project (as shown above in the logs: 3653 code files requiring 56.614 seconds to load).
77
Help / Re: Why does the code editor window close after saving a file?
« Last post by Pecan on April 18, 2026, 07:19:27 am »Where can I download the source causing the problem.
I want to re-create the problem while running CB under the debugger.
Also, are you sure that the Code Completion plugin is disabled?
That wait after saving feels like a timer pop then running some code.
Or a lock on the main gui code being released.
Very suspicious of a bug from last century.
I want to re-create the problem while running CB under the debugger.
Also, are you sure that the Code Completion plugin is disabled?
That wait after saving feels like a timer pop then running some code.
Or a lock on the main gui code being released.
Very suspicious of a bug from last century.
78
Help / Re: Why does the code editor window close after saving a file?
« Last post by Stratelier on April 18, 2026, 05:56:35 am »Where did that copy of CodeBlocks come from?
From the official Downloads page, via the SourceForge link. By now I've also downloaded it from the dAppCDN link -- apparently, the two installers are not byte-identical (with the SourceForge installer reported as 52,312,337 bytes; dApp installer 52,313,001 bytes).
If it helps, this is also the information reported under "Help > About" :
Code
Name : Code::Blocks
Version : 25.03-r13644
SDK Version : 2.25.0
Scintilla Version : 3.7.5
Author : The Code::Blocks Team
E-mail : info@codeblocks.org
Website : https://www.codeblocks.org
OS : Windows 10 (build 19045), 64-bit edition
Scaling factor : 1.000000
Detected scaling factor : 1.000000
Display PPI : 96x96
Display count : 1
Display 0 (\\.\DISPLAY1): XY=[0,0]; Size=[1366,768]; Primary
wxWidgets Library (wxMSW port)
Version 3.2.7 (Unicode: wchar_t, debug level: 1),
compiled at Mar 25 2025 17:16:27
Runtime version of toolkit used is 10.0.19045.
There are no active plugins
Disabling all plugins (temporarily) was my choice here.
Quote
Please start CodeBlocks with the '/d' parameter to create the debug log.
After the windows disappears please show us the data written to the CodeBlocks log.
Click on the "CodeBlocks" log tab, place the mouse in the log window and scroll upward to see the data.
Right-click and choose "copy contents to clipboard".
Paste that data to use between code tags (The # icon above a reply box).
Do the same with the "Code::Blocks debug" tab and window.
We'd like to see what is being logged when you save a file.
Thanks for your reporting and patience.
On it.
...maybe I should have chosen a smaller project than GIMP to demonstrate with, but regardless, upon saving a file this appears in the Codeblocks main log:
Code
wxDir::GetAllFiles 0.824000 s
makePathsRelativeIfNeeded 0.807000 s
filterOnWildcards 0.318000 s
Loading directories took 2.034000 s
Adding took 10.537000 s
Loading globs took: 12.699000 s
ProjectManagerUI::RebuildTree took 0.577 seconds
Rebuilding tree took: 0.578000 sNothing at all appears in the Debug log when saving.
Ten seconds is a noticeable wait, but the editor window is still open prior to that.
And this is the full log (open project, open a file, dummy edit, save file):
Code
Opening C:\Users\strat_000\Projects\Gitlab\gimp-master\GIMP 3.dev\GIMP 3.dev.cbp
wxDir::GetAllFiles 0.782000 s
makePathsRelativeIfNeeded 0.836000 s
filterOnWildcards 0.321000 s
Loading directories took 1.949000 s
Adding took 11.026000 s
Done.
cbProject::Open() took: 42.479 seconds.
wxDir::GetAllFiles 0.811000 s
makePathsRelativeIfNeeded 0.831000 s
filterOnWildcards 0.325000 s
Loading directories took 1.984000 s
Adding took 11.021000 s
ProjectManagerUI::RebuildTree took 0.560 seconds
ProjectManager::SetProject() took: 13.670 seconds.
ProjectManager::LoadProject took: 56.614 seconds.
wxDir::GetAllFiles 0.818000 s
makePathsRelativeIfNeeded 0.829000 s
filterOnWildcards 0.318000 s
Loading directories took 1.983000 s
Adding took 10.544000 s
Loading globs took: 12.651000 s
ProjectManagerUI::RebuildTree took 0.629 seconds
Rebuilding tree took: 0.631000 sFull debug log from the same:
Code
Loading project file...
Parsing project file...
Loading target Debug
Loading target Release
Loading project files...
3653 files loaded
Done loading project in 10547 ms
Project's base path: C:\Users\strat_000\Projects\Gitlab\gimp-master\GIMP 3.dev\
Project's common toplevel path: C:\Users\strat_000\Projects\Gitlab\gimp-master\
Mozilla universal detection engine detected 'Pure *ASCII*'.
Final encoding detected: Windows Western European (CP 1252) (ID: 33)
Conversion succeeded using wxEncodingConverter (buffer size = 12559, converted size = 12563.
79
Help / Re: Why does the code editor window close after saving a file?
« Last post by Pecan on April 18, 2026, 03:55:01 am »Where did that copy of CodeBlocks come from?
Please start CodeBlocks with the '/d' parameter to create the debug log.
After the windows disappears please show us the data written to the CodeBlocks log.
Click on the "CodeBlocks" log tab, place the mouse in the log window and scroll upward to see the data.
Right-click and choose "copy contents to clipboard".
Paste that data to use between code tags (The # icon above a reply box).
Do the same with the "Code::Blocks debug" tab and window.
We'd like to see what is being logged when you save a file.
Thanks for your reporting and patience.
Please start CodeBlocks with the '/d' parameter to create the debug log.
After the windows disappears please show us the data written to the CodeBlocks log.
Click on the "CodeBlocks" log tab, place the mouse in the log window and scroll upward to see the data.
Right-click and choose "copy contents to clipboard".
Paste that data to use between code tags (The # icon above a reply box).
Do the same with the "Code::Blocks debug" tab and window.
We'd like to see what is being logged when you save a file.
Thanks for your reporting and patience.
80
Help / Re: Why does the code editor window close after saving a file?
« Last post by Stratelier on April 18, 2026, 01:34:14 am »This issue has not been reported elsewhere before, and it is very strange. May the destination folder (or file) be write-protected?
The file is definitely not write-protected, since I am successful in saving it (though the editor window closes after saving).
Apparently the folder is marked as read-only (I had little incentive to even check for this going in) -- though removing the lock makes no difference, the editor window still closes after a successful save.
If I have multiple files open in the editor, make changes to only one file and save it (either from the menu or with the keyboard shortcut, the effect is the same), the editor window ultimately closes in its entirety.
If I have multiple files open in the editor, make changes to two or more files, then Save one of the files, the save is successful, but the file is closed after saving, and then CB prompts me to save the other file -- implying something is clearly trying to close the entire editor window after the successful save. If I cancel at this point, the interface is left as-is, minus the tab for the file that was just saved.
Quote
Are you saving the file with the drop down menu, or using a key combo?I get the same result either way -- save is successful, then the editor window closes.
Have there been any modification/overrides made to the keyboard?
One important detail is that when I save a file, the editor window's GUI refreshes after saving (yellow margin indicators turn green) and THEN the editor window closes (after some delay). If I try to close the editor window directly and save changes when prompted, the tab disappears immediately, then the editor window closes entirely after a delay.
Oh, right, that delay may be another important detail; see new attachment (unsaved at left, saved at right, moments before the editor window closes).