Task in "Running" state a day after stderr says it failed

I have a workflow (ID 48e54c59-9d56-4dd7-8745-a5cca7ccaa30) where a task failed a day ago according to the stderr:

Exception in thread Thread-3:
Traceback (most recent call last):
  File "/opt/conda/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/opt/conda/lib/python2.7/threading.py", line 754, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/opt/conda/lib/python2.7/site-packages/multiprocess/pool.py", line 389, in _handle_results
    task = get()
  File "/opt/conda/lib/python2.7/site-packages/dill/dill.py", line 277, in loads
    return load(file)
  File "/opt/conda/lib/python2.7/site-packages/dill/dill.py", line 266, in load
    obj = pik.load()
  File "/opt/conda/lib/python2.7/pickle.py", line 864, in load
    dispatch[key](self)
  File "/opt/conda/lib/python2.7/pickle.py", line 982, in load_binstring
    self.append(self.read(len))
MemoryError

It looks like it ran out of RAM. The task is still listed in the "Running" state. Can I assume that this VM was terminated or is there a way to check?

Thanks.