leewp14 I guess there's not much I could do then?
It's not something that would be easy for a ordinary mortal. Or even for a lot of programmers, for that matter. It would probably make more sense to bring it to the attention of that application's developers.
There are development tools that help in identifying resource leaks by taking a snapshot of memory before running a program, then another snapshot of memory after the program has exited. Comparing the before and after snapshots can confirm that the problem exists, and how bad it is.
Figuring out what to change to stop it from happening can get a bit more complicated.
EDIT: Full disclosure ... my experience in fixing these is all with Windows executables and DLLs. If this description doesn't apply to Linux, someone please correct me.