You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Policies with too high nesting depth are not rejected: It is possible to create small inputs that cause extreme memory usage (in practice: OOM kill or std::bad_alloc)
#7
Open
practicalswift opened this issue
Aug 29, 2019
· 1 comment
Policies with too high nesting depth are not rejected: It is possible to create small inputs that cause extreme memory usage (in reality: OOM) and long running time.
The ./threshold.py 9 example below is 252 bytes and causes a memory consumption of 18.5 GB RAM and a running time of more than ten minutes.
The ./threshold.py 10 example below is 280 bytes will hit OOM on most systems before having a chance to finish.
The following script can be used to construct pathological inputs based on nested thresh:
The text was updated successfully, but these errors were encountered:
practicalswift
changed the title
Policies with too high nesting depth are not rejected: It is possible to create small inputs that cause extreme memory usage (in practice: OOM)
Policies with too high nesting depth are not rejected: It is possible to create small inputs that cause extreme memory usage (in practice: OOM kill or std::bad_alloc)
Aug 30, 2019
Policies with too high nesting depth are not rejected: It is possible to create small inputs that cause extreme memory usage (in reality: OOM) and long running time.
The
./threshold.py 9
example below is 252 bytes and causes a memory consumption of 18.5 GB RAM and a running time of more than ten minutes.The
./threshold.py 10
example below is 280 bytes will hit OOM on most systems before having a chance to finish.The following script can be used to construct pathological inputs based on nested
thresh
:Example runs with varying levels of nesting:
The text was updated successfully, but these errors were encountered: