unfreed signals

Just a quick question because i couldn't find an answer anywhere.

This happens when i start scummvm intentionally with a wrong command flag:
scummvm -version (doesn't exists, only --version is known). If i do that i get this message everytime:


1) What exactly does that mean and how could one fix it?
2) Is it some kind of aAMigaOS4 specific memory leak?
3) Does it mean something "bad" needs to be fixed or could one ignore it?
4) If it was to be fixed where does one need take a look at the source?

Just checking if i can ignore that or if i should fix it.

btw, i've seen this unfreed signals messages on lots of programs, can't remember right now which ones

EDIT:
Nevermind

Basically what is happening is this....

A shell runs in its own process, when you start a program from that shell
process, the program uses the shells process to execute, the shell code
goes to sleep during the program execution, when the program ends,
the shell code resumes and is ready to take another command line.

So, when the program is being executed, it's apparently allocating a signal,
such as would happen if the program was to allocate a message port or
other such activity during its operation.

However, the program is exiting without freeing all the resources it allocated,
so the shell notices this and posts the message because as the shell process
is continually reused by subsequent programs, it will eventually run out of
signals to allocate (only 16 user signals available) and all sorts of bad juju
will happen if that occurs.

So, yes, the program being run is doing something it shouldn't when it exits
in an unexpected way.

@colinw

Heh, even i understand this

Thanks a lot, Colin

@Raziel

Does it exit here, in usage function: https://github.com/scummvm/scummvm/blo ... base/commandLine.cpp#L197

Basically ScummVM doesn't seem to try any cleanup, unless there is some atexit() lurking somewhere.

@Capehill

Will relay to the app devs, thanks for the pointer