--execution-timeout fails

Description

Using the --execution-timeout flag fails under large loads and/or on an unknown set of addresses. I am running mythril on a large set of addresses with a execution-timeout flag of 900. However, under top, there are two running instances of mythril that have been running for 861:55:86+ and 1580:41+ (minutes:seconds.hundredths).

How to Reproduce

I’m unsure of how to reproduce this as I’m unable to determine the addresses they failed on, or the true root cause. After I kill the processes, then maybe there may be a stack trace, but I don’t think that this will reveal what addresses they failed on.

Expected behavior

Mythril should stop trying to symbolically execute after 900 seconds has elapsed.

Screenshots

EDIT: I actually am recording what addresses give what output (e.g., success, ERROR, CRITICAL, etc.), so I can determine if this bug is due to a specific contract, the volume of contracts I am scanning, or the method (i.e., multiprocessing with docker run commands) by checking my original file full of addresses and seeing what contract did not complete (i.e., did not get written to any of files/“bins” above).

[Danc2050]

I believe this is actually an issue with Docker, not mythril.

Below is optional reading I originally was cleaning up old containers with the command docker system prune in a crontab. However, what I believe ended up happening was the crontab would run when a Docker container was being started and marked as inactive, but then it would start, but not be able to run since it was marked for deletion. Still haven’t proven this, but I get an error message that seems to hint at this being hte issue. Since using the --rm command to remove the container instead of the crontab, I haven’t had any issues of a myth process running past the execution-timeout specified. I’ll bring this to the Docker people instead of here.

[norhh]

@chetansaini1234 can you elaborate on the issue.