Program terminated with signal SIGKILL problem

[Aisheh Al-Sadi]

Hi,

My application stopped suddenly, I tried to trace the problem using gdb tool and it gave me this message
"Program terminated with signal SIGKILL, Killed. The program no longer exists."
I tried to used valgrind tool, but the computer doesn't respond when reach to the problem.
What is the possible problem ? Is it from my code or from Unix?

Thanks,

[Thanassis Boulis]

Well, something is killing the simulation. If this is not you, it might be the system that tries to protect other running processes from a runaway process (your simulation). It might be another tool that you have for this purpose. You can check system logs for messages about killing your simulation.

--
You received this message because you are subscribed to the Google Groups "Castalia Simulator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to castalia-simulator+unsub...@googlegroups.com.
To post to this group, send email to castalia-simulator@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/castalia-simulator/cf238fac-61e7-4ceb-9dcd-661c74b8353c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Aisheh Al-Sadi]

 I found this part related to Castalia in syslog file

CastaliaBin
Aug 24 16:08:15 aisha-Vostro-430 kernel: [ 6458.559212] Out of memory: Kill process 2814 (CastaliaBin) score 908 or sacrifice child
Aug 24 16:08:15 aisha-Vostro-430 kernel: [ 6458.559214] Killed process 2814 (CastaliaBin) total-vm:7457780kB, anon-rss:3582684kB, file-rss:0kB

On Thursday, August 25, 2016 at 7:04:32 AM UTC, Athanassios (Thanassis) Boulis wrote:

Well, something is killing the simulation. If this is not you, it might be the system that tries to protect other running processes from a runaway process (your simulation). It might be another tool that you have for this purpose. You can check system logs for messages about killing your simulation.

On 25 August 2016 at 16:36, Aisheh Al-Sadi <aishe...@gmail.com> wrote:

Hi,

My application stopped suddenly, I tried to trace the problem using gdb tool and it gave me this message
"Program terminated with signal SIGKILL, Killed. The program no longer exists."
I tried to used valgrind tool, but the computer doesn't respond when reach to the problem.
What is the possible problem ? Is it from my code or from Unix?

Thanks,

--
You received this message because you are subscribed to the Google Groups "Castalia Simulator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to castalia-simulator+unsub...@googlegroups.com.

To post to this group, send email to castalia-...@googlegroups.com.

[Thanassis Boulis]

So the simulation is using a lot of memory, and the system kills it. The log shows that it was using more than 7GB of memory! 

Most probably there is something wrong with the code you introduced. You are allocating a lot of memory without freeing it. 

 

Another possibility would be you are defining mobile nodes in a huge field with small spatial resolution. But then you would get the crash during initialisation of the simulation. You mentioned that the simulation keeps on going for a while before it crashes. So look at your code for potential memory leaks.

 

On 25 August 2016 at 18:11, Aisheh Al-Sadi <aishe...@gmail.com> wrote:

 I found this part related to Castalia in syslog file

CastaliaBin
Aug 24 16:08:15 aisha-Vostro-430 kernel: [ 6458.559212] Out of memory: Kill process 2814 (CastaliaBin) score 908 or sacrifice child
Aug 24 16:08:15 aisha-Vostro-430 kernel: [ 6458.559214] Killed process 2814 (CastaliaBin) total-vm:7457780kB, anon-rss:3582684kB, file-rss:0kB


On Thursday, August 25, 2016 at 7:04:32 AM UTC, Athanassios (Thanassis) Boulis wrote:

Well, something is killing the simulation. If this is not you, it might be the system that tries to protect other running processes from a runaway process (your simulation). It might be another tool that you have for this purpose. You can check system logs for messages about killing your simulation.

On 25 August 2016 at 16:36, Aisheh Al-Sadi <aishe...@gmail.com> wrote:

Hi,

My application stopped suddenly, I tried to trace the problem using gdb tool and it gave me this message
"Program terminated with signal SIGKILL, Killed. The program no longer exists."
I tried to used valgrind tool, but the computer doesn't respond when reach to the problem.
What is the possible problem ? Is it from my code or from Unix?

Thanks,

--
You received this message because you are subscribed to the Google Groups "Castalia Simulator" group.

To unsubscribe from this group and stop receiving emails from it, send an email to castalia-simulator+unsubscribe@googlegroups.com.

To post to this group, send email to castalia-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/castalia-simulator/cf238fac-61e7-4ceb-9dcd-661c74b8353c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Castalia Simulator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to castalia-simulator+unsub...@googlegroups.com.

To post to this group, send email to castalia-simulator@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/castalia-simulator/c0f0a152-9dd9-4a3d-984b-d5b589a3e385%40googlegroups.com.

[Aisheh Al-Sadi]

I gave the computer a long time to get out from freeze, to see if Valgrind give any info.

==5060== LEAK SUMMARY:

==5060==    definitely lost: 0 bytes in 0 blocks

==5060==    indirectly lost: 0 bytes in 0 blocks

==5060==      possibly lost: 236,443 bytes in 96 blocks

==5060==    still reachable: 1,987,595 bytes in 624 blocks

==5060==         suppressed: 0 bytes in 0 blocks

As I understood from Valgrind docs that:

"definitely lost" means your program is leaking memory -- fix those leaks!

"indirectly lost" means your program is leaking memory in a pointer-based structure. (E.g. if the root node of a binary tree is "definitely lost", all the children will be "indirectly lost".) If you fix the "definitely lost" leaks, the "indirectly lost" leaks should go away.

"possibly lost" means your program is leaking memory, unless you're doing unusual things with pointers that could cause them to point into the middle of an allocated block.

In my program I am using only vectors (i..e. push, erase) so there is no chance to play with pointers!

Also I noticed that ALL the memory lost were in ( /usr/bin/python2.7)

Thanks,

[Thanassis Boulis]

Your memory growing does not necessarily mean that you have a leak. 

A leak is when you are losing track of your pointers without freeing them. You can simply allocating a lot new memory in arrays, vectors, whatever, and still be able to access it, so valgrind will not complain for a leak. You have to find what allocates so much memory in your program.

--
You received this message because you are subscribed to the Google Groups "Castalia Simulator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to castalia-simulator+unsub...@googlegroups.com.
To post to this group, send email to castalia-simulator@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/castalia-simulator/5bbd6c09-6fa6-4437-b9d5-f5f154462fee%40googlegroups.com.