An unhandled exception ...

[oBFusCATed]

Yes, but this shouldn't cause a crash. Is this crash happening only on win32? Can you reproduce this with win64?

[LETARTARE]

Summary of the latest tests to date :

I use two files :

1- 'All_codeblocksLF.po' with end of line 'LF'.
2- 'All_codeblocksCRLF.po' with end of line 'CRLF'

and always 'cb-12180' compiled with the mentioned 'gcc'.
1- I load the file in the editor of CB
2- I'm modifying it.
3- I'm saving him.

Window OS:
CB->Editor->Ensure Consistent EOLs = Yes
CB->Editor->End of Line : CRLF
Win7-64bits :  gcc-810-32 bits, wx-313,  file 'LF' => crash, file 'CRLF' => good
Win7-64bits :  gcc-810-64 bits, wx-313,  file 'LF' => crash, file 'CRLF' => good
Vista-32bits :  gcc-810-32 bits, wx-313,  file 'LF' => crash, file 'CRLF' => good
Exception message for the crash.

Linux OS (OpenSuse-Leap-15.1 last update)
CB->Editor->Ensure Consistent EOLs = Yes
CB->Editor->End of Line : LF
gcc-750-64bits, wx-303 => file 'LF' => good, file 'CRLF' => crash
No exception message for the crash !
Under OpenSuse-Leap-15.1 , the file with 'CRLF' crashes the system if the CB application is not destroyed before the memory is saturated !

You can see that the error occurs if the file does not have the editor's line endings

I forgot the files...

[oBFusCATed]

What are the exact steps to reproduce this?

I've done:
1. loaded the LF file. Which was slow because of the spellchecker.
2. executed Edit -> End-of-line mode -> Windows (CR & LF). This took less then ten seconds, but finished successfully. No excessive memory usage.

[LETARTARE]

Which operating system ?  I'm guessing Win??

If with CB you transform the end of lines in accordance with the operating system: no problem.
If you don't do the transformation: crash

The default is to use a badly coded file at the end of the line: see the examples in my previous message.
If the end of the lines don't match, I think Scintilla is detecting the wrong file!

[oBFusCATed]

My OS Linux, 64bit.
Please post step by step instructions.

Code

1. start codeblocks
2. open this
3. do this
4. 
5. 

If you want this fixed please fill steps 2-5. I've spend too much time trying to reproduce it and if I'm not able to reproduce it in 5 minutes, I'll switch to doing something else.

[LETARTARE]

My test wit Linux :
- Linux OS (OpenSuse-Leap-15.1 last update) with 6GB memory and 2GB swap
- cb-12180 compiled with gcc-750-64bits, wx-303

1- start cb-12180 wit no project
    CB->Editor->Ensure Consistent EOLs = Yes
    CB->Editor->End of Line : LF
2- load 'All_codeblocksCRLF.po' with end of line 'CRLF'
3- add a space and save the file
4- the cursor indicates an important background task and the memory used increases linearly
5- ATTENTION : you must kill CB before reaching maximum memory or the system will crash !
   No message appears !

I had to reinstall a copy of my OpenSuse disk after this mishap !

[oBFusCATed]

It seems to be caused by the "ChangeBar" patches to Scintilla we're using. It is not crashing on my machine, but uses a lot of memory, so I guess if you look in dmesg you'll see an OoM message. You can improve the testing time of this by disabling swap. Without swap when you get out of memory you'll get a direct crash. If you want to prevent crashes but you have a lot of time you could setup bigger swap.

I'm not sure how to resolve the problem, I'm not really familiar with the patch and should investigate it.

[LETARTARE]

Thank you for the test that partially corroborates mine.
Maybe contact the developer who maintains 'Scintilla'?

[oBFusCATed]

This is the plan, but talking to Neil is not the most pleasant or fruitful experience.