`myth -j` creates massive log file
See original GitHub issueSymptom
Calling myth with -j
on my project (300 LOC in total) took very long time and generated over 90mb of json object dump
Version
0.16.31
Steps to recreate
git clone https://github.com/makoto/blockparty.git
cd blockparty
git checkout 1c2884cc9262c5fc8aba026720b289620c00bceb
myth -j ./statespace.json contracts/Conference.sol --max-depth 8
$ ls -ltr statespace.json
-rw-r--r-- 1 makoto staff 92582854 5 May 20:52 statespace.json
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Multiple log files and why they're bad - Paul S. Randal
If the log files don't exist, they must be created and zero-initialized, and twice if you restore a diff backup too as both...
Read more >Why is my SQL Log File Huge? - DallasDBAs.com
HUGE Log files and how to troubleshoot: The single most common question I have encountered in 18+ years of working with SQL Server:....
Read more >A beginner's guide to SQL Server transaction logs - SQLShack
A transaction log is a file – integral part of every SQL Server database. It contains log records produced during the logging process...
Read more >IndexError: pop from empty list on max-depth · Issue #111 ... - GitHub
Running the following command myth -xia 0xcafe1a77e84698c83ca8931f54a755176ef75f2c -o json results in large RAM consumption during analysis (roughly 8GB on ...
Read more >How do you clear the SQL Server transaction log?
Instead of shrinking your log file to some small amount and letting it constantly autogrow at a small rate on its own, set...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks Makoto, we’ll try to address this soon.
I assume this will be solved if we implement the wordlist algorithm instead of recursive
_sym_exec
.