Recent Posts

1

General (but related to Code::Blocks) / Re: Generate a file '*_linux.cbp' to '*_win.cbp' or vice versa

« Last post by Miguel Gimenez on Today at 09:05:57 am »

Delayed profile spammer predictbong reported to moderator.

2

Help / Re: c++23

« Last post by Miguel Gimenez on Today at 09:03:23 am »

Delayed profile spammer rundowndrag reported to moderator.

3

Help / Re: Code editor window closing after saving files (related to very large projects)

« Last post by Stratelier on Today at 02:03:11 am »

Oh I've definitely encountered "memory thrashing" before (starting around >90% RAM usage), but when it happens it is typically far worse than what I'm seeing here with CB.

As for ordinary day-to-day usage, I know this bug cast a rather bad first impression of the editor, but I'm also noticing various little mundane details that don't sit as well with me.  Like the top-level split between .c and .h files in the project panel.

I'm willing to help stay and debug for a bit, but I'd probably need instruction on building CB from its source first because as long as I'm the only one it's actively happening to, I'm also the only one that can truly dive into it to research what is going wrong where.

I can find no code that saves the files ok and then closes them.

If I have two files open & modified, the "save changes?" prompt is a good breakpoint where I should be able to fetch the call stack and find exactly WHERE it is trying to close the editor window.

In the meantime, viewing Task Manager there is a "normal" CPU spike while saving a file (in 1 of 4 CPU cores) but it is very localized to CB itself (not affecting other processes / system at large).  I additionally sometimes see the little "leaf" icon next to its status, indicating that (as a UWP process) the system has occasionally suspended it (by force?) -- see attachment.

4

Help / Re: c++23

« Last post by killerbot on Yesterday at 10:24:32 pm »

my advice: don't use pcm.


I have several projects using C++23 in CB, even C++26.

5

General (but related to Code::Blocks) / Re: Generate a file '*_linux.cbp' to '*_win.cbp' or vice versa

« Last post by Miguel Gimenez on Yesterday at 11:44:29 am »

Profile spammer olenna reported to moderator.

6

General (but related to Code::Blocks) / Re: Generate a file '*_linux.cbp' to '*_win.cbp' or vice versa

« Last post by olenna on Yesterday at 11:13:07 am »

There is no official tool that reliably converts a *_linux.cbp project into a *_win.cbp.

7

Help / Re: Cannot find the compiler

« Last post by thereforerepair on Yesterday at 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.

8

General (but related to Code::Blocks) / Re: Generate a file '*_linux.cbp' to '*_win.cbp' or vice versa

« Last post by predictbong on Yesterday at 09:08:56 am »

I agree with your point. Different operating systems also offer different linking options. It's perfectly possible to select the appropriate file across systems.

9

Help / Re: c++23

« Last post by rundowndrag on Yesterday at 09:05:03 am »

The talk about C++23 features piqued my interest, especially the emphasis on enhancing code readability and performance. Are there any particular examples of this method having a big influence on projects?

10

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:

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.