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
The current way the extension runs the proofs is to line them up in a queue and run them one by one. But this is not necessary, this can optimized for cases when a user wants to run proofs on the entire crate.
What's to be investigated is how much memory intensive this might be. Some proofs already are memory and stack intensive enough to cause crashes to the extension and stop verification. If there's a timeout mechanism of some sort then maybe the process for running that specific proof can be stopped while parallel running the other proofs.
The text was updated successfully, but these errors were encountered:
The current way the extension runs the proofs is to line them up in a queue and run them one by one. But this is not necessary, this can optimized for cases when a user wants to run proofs on the entire crate.
What's to be investigated is how much memory intensive this might be. Some proofs already are memory and stack intensive enough to cause crashes to the extension and stop verification. If there's a timeout mechanism of some sort then maybe the process for running that specific proof can be stopped while parallel running the other proofs.
The text was updated successfully, but these errors were encountered: