what!?
ik this doent go here cause it doesnt go anywhere! but i went to the customer support page to see problems other people had, and i came across something someone put that freaked me out! i clicked on it and it was only a technical issue, but i couldnt get it out of my mind! it said: "
Child Killed: Unknown signal. The application will exit now"
if u know something about it, please say, i know its probably not important, but i dont know... its weird... and scary...
It's like someone waved a huge "T R O L L" flag on that one. If a child was killed it wouldn't be posted on a game forum.
Yeah, I've actually gotten that message a few times. Alarmed me the first time I saw it, too 0__0
I'm sure the more tech-savvy peeps are gonna explain way better, but basically it's a specific error that occurs in programs on pcs. One that, if I understand it correctly, glitches and terminates the program for that session. WHY the coders decided to give that specific error THAT kind of a name, idk.:/
In any case it's not talking about real children thank goodness. it's just a term in coding. Which I know nothing about xD
Hope that helps!
Simply put: Applications can launch other applications. These applications are referred to as "children" of the "parent" application. When a program has been "killed", that means it has been forcefully exited. Therefore, "Child killed" in this case means that a program which was launched by another one was unexpectedly terminated. Does that help?
Yep that makes sense and helps, thanks!
LOL. Yes that one's pretty funny.
In object-oriented programming, Parent-child classes are classes that have been linked together. The parent contains information, which the child 'inherits' from the parent. For example, a child may be 'night fury', which inerits info from the parent 'dragon'.
"Child killed" means that the child has been terminated, aka stopped. The game needs that 'child' in order to run, but because the child has been 'killed', it cannot inherit anything from its parent, which will crash/close your game.
The error in itself occurs rarely and isn't anything to worry about.
ETA: correction
I'm not a programmer, I just live with one, so correct me if I'm wrong. :þ
It's a weird coding error.
Antiviruses like McAfee is known for intercepting NBU processes, both the latter or manually ending processes in Task Manager.
Unless you're consistently getting this error it shouldn't be anything to worry about.
Oh yeah, that error. Varku and Dragonriders Fury have explained the parent-child relationship correctly, though I was wondering if you could post a screenshot of the error dialogue so I can see if it mentions anything else that could help figure out what's causing it? A friend of mine runs into that error frequently since the Thawfest update and his error seems to be what's called a "segfault": when an application attempts to access a restricted part of the system memory. Usually in cases like these, all you can do is send a support ticket/wait for the next patch, there isn't much that can be done on the player's end.
Ditto on the error screenshot, or better, the log entry in the event viewer if possible.
But yeah if it's a segfault or other memory-related error you're probably out of luck. All sorts of things can cause those, but I'm going to assume it's the game in this case. You can try to update your OS and drivers, but I think people who have this error a lot will just have to wait for a fix.