User forums > Help

Code editor window closing after saving files (related to very large projects)

<< < (3/3)

Pecan:
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?
    }

--- End code ---

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.

Stratelier:
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.


--- Quote ---I can find no code that saves the files ok and then closes them.
--- End quote ---

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.

Navigation

[0] Message Index

[*] Previous page