That definitely shouldn't be happening. The usual cause is starting up the IDE from a shell and- for some reason- either closing the shell session or inadvertently feeding it a ^C (or some other signal).
No, I ran laz from kde startup menu.
Apart from that... I'd suggest running top to make sure that you're not heading towards resource exhaustion (which might cause the kernel to start killing processes) and to check your hardware: note Torvalds' recent experience where something he initially thought was a kernel problem turned out to be dud DIMMs (and the expected rant about the paucity of quallity ECC DIMMs).
MarkMLl
I an in a VM 4Gb, and I was editing just that file, and sometimes running the program inside the IDE to generate an xml file on the filesys, I have difficulty to think about resource fillup.
Also, the stuff of the DIMMs, might be of course but this machine is kinda new and I did not see any other problem on it so far (and I also ran couple of times the bios mem inspection tools)
Anyway, if it happens again, I will try to remain calm (difficult
) and make up a more serious analysis of reproducibility.
To be honest? I still have 101% respect and faith in lazarus no matter what.