On 19/08/2019 18.54, Bernhard Voelker wrote:
On 8/17/19 8:26 AM, Carlos E. R. wrote:
The coredumps of this process stopped when I first applied this command a year or two ago.
ahem, you're getting core dumps for an open source program for such a long time, and you're in contact with the developer and he/she doesn't fix it? Weird ...
Yep. He develops in Windows, probably has no toolset to debug in Linux. That's not the worst problem, though.
BTW: if it's a closed source program, then still avoiding to write huge core files is only half of the solution. The program in question could already have gone wild before actually triggering a coredump in the kernel.
Certainly. Some of the crashes were because all memory was used. I could limit its memory usage, too, forcing it to crash earlier. But that particular problem has not happened since some months. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)