I'd recommend you learn the command line utilities before you go errantly killing a process. For now, if you haven't already you may just want to restart the server after safely closing what you can.
FMSADMIN RESTART WPE
is the command to restart your web publishing engine via command line.
As for the log, there's the regular log inside of the server admin console. You can also check your operating system log.
From what I've dealt with in the past, timed out or poorly disconnected sessions and file downloads via the WPE can cause the RAM pool to fill up. Usually I've been able to restart the WPE via command line, however in extreme cases it has required a restart. Double check your security privileges for WPE connections to make sure you have a valid session timeout set.
Thank you Mike, if this happens in the future i will run the command prompt and not immediately end the process, but how can I check what is causing the issue(if there is a way)