BSOD because of CudaText

5ezsfh78 · Post by **5ezsfh78** » 27.04.2022 14:35

Should be Lazarus app's notorious access violation error but this time more serve. Or could be in the shell extension. Right click on a simple text file, choose Open with CudaText and suddenly Windows goes to BSOD and after restart my text file is corrupted. The size in bytes is still the same but the content is gone. Open with CudaText or any other text editors only show an empty text file. You should audit your code. Running a static analyzer might help. But I afraid the error is of the LCL itself. I have used many Lazarus apps and most if not all of them will show access violation after a while. Sometimes it's trivial, sometimes it's fatal like this.

Sincere,
A long time user

p/s: I will switch to Notepad++ for a while. Bye.

ertank · Post by **ertank** » 27.04.2022 18:05

I cannot repeat that. I am using Windows 11 64bit dev release. CudaText is latest 64bit.
I frequently use open with CudaText and never ever hit any access violation or BSOD.

BTW, my experience, BSOD mostly raises because of hardware faults rather than software (unless software is a device driver).

main Alexey · Post by **main Alexey** » 27.04.2022 20:48

I did not see BSOD either. I only see some OS hangs on Linux, during debugging (reason was Linux component).

EDIT
the reason is 'CudaText shell extension'? so just un-register it, via Batch file, and don't register it anymore, app is usable without it!

friend · Post by **friend** » 03.05.2022 11:53

You're pulling ideas out of your derrière and transforming them into words; your post is a huge pile of dung.

>Lazarus apps's notorious access violation
>Windows goes to BSOD
>You should audit your code. Running a static analyzer might help
>I have used many Lazarus apps
>most if not all of them will show access violation after a while

How did you manage to fit so much stupidity in one single post?
Unsurprising for a M$ Windows user who writes "app".

main Alexey · Post by **main Alexey** » 03.05.2022 15:27

Users, please do not humilate other users; I want the forum to be the technical forum only...

main Alexey · Post by **main Alexey** » 03.05.2022 15:33

Also note that last versions have fixed 'hidden access violation' (that happened in a thread and was not visible to the user). maybe that 'access violation' was the reason of BSOD, I'm not sure.

1.160.0 (2022/04)
+ add: more stability of the multi-threaded parser (before, file ~/cudatext.error could appear, please report if that file appears again with new info)