-
-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache file read failure #22
Comments
I can reproduce the problem with the attached cache file. Thanks for reporting this! Will investigate. |
Looks like that old parser was a bit too simplistic for some fringe cases. This should be fixed now. There is some performance impact, though: Unlike previously, we now have a regexp search & replace for each cache line to avoid double slashes (which QUrl doesn't seem to handle well). |
I was unsure about this for a while, but I can now reproduce it. This is unrelated to this original issue, though: This is a problem in the internal cache writer class. When I generate the cache file with the supplied qdirstat-cache-writer script, I get the exact same result (7.8 GB total) for my root file system no matter if qdirstat reads it directly from disk or if it reads the cache file. When I generate that cache file with the "File" -> "Write Cache File" menu actions, though, the resulting cache file contains only 457 MB worth of files. I will clone this into a separate issue to keep track of this. |
Cloned issue: #23 |
Program fails to read/load complete cache file..
Environment is Ubuntu 16.04 VM ( virtualbox ) with QT 5.7 ( opensource )
Cache file attached..
qdirstat.cache.gz
File generated by pointing at root (/) mount point while running as non-root user.
Treemap builds and displays, Cache file save seems to write "correct" information.
When attempting to read the cache file, the first (/) directory and the 2 file links are the only things processed / displayed..
Log file is full of the "cannot find parent" messages referenced in the other cache file issue reported
qdirstat-1000.log.tar.gz
The text was updated successfully, but these errors were encountered: