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
I ran both hindsight_gui.py and the command line version hindsight.py to test this issue, with identical results.
Running from git master at commit 13b7a64 (when run, it announces v20201120) in macOS Catalina under Python 3.9.0 with target browser macOS Catalina Chrome Version 87.0.4280.141, it found 0 cache records.
I specified Input Path: /Users/sidney/Library/Application Support/Google/Chrome/Default and Cache Path: /Users/sidney/Library/Caches/Google/Chrome/Default/Cache/.
I ran hindsight_gui.py and entered the above paths in the browser GUI window, then clicked Run.
For the command line form of the test, I used the command
Enter /Users/YOURUSERNAME/Library/Application Support/Google/Chrome/Default in the Input Path box
Enter /Users/YOURUSERNAME/Library/Caches/Google/Chrome/Default/Cache in the Cache Path box
Click on the Run button
Expected results: more than 0 cache records found Actual results: 0 cache records found, and hindsight.log shows an error Failed to parse index block file
The text was updated successfully, but these errors were encountered:
The error message in the log file comes from an exception that is raised in the initialization of class CacheBlock in chrome.py when it fails to find a magic number in the file named index. The most recent version of Chrome for macOS that I found that used that format for Cache/index was Chrome version 69 from September, 2018. The next version I could test was version 72 from March 2019. That one and all versions since use a very different index format which has index being a small 24 byte file, and the actual cache index data being in a file in a subdirectory, Cache/index-dir/the-real-index
Hey there, thanks for the report! I've seen this "new" SimpleCache in Linux for a while, but hadn't seen it in macOS before. I'll open an issue here to track it, as if it's getting more prevalent, I need to prioritize getting it into Hindsight.
I ran both hindsight_gui.py and the command line version hindsight.py to test this issue, with identical results.
Running from git master at commit 13b7a64 (when run, it announces v20201120) in macOS Catalina under Python 3.9.0 with target browser macOS Catalina Chrome Version 87.0.4280.141, it found 0 cache records.
I specified Input Path:
/Users/sidney/Library/Application Support/Google/Chrome/Default
and Cache Path:/Users/sidney/Library/Caches/Google/Chrome/Default/Cache/
.I ran hindsight_gui.py and entered the above paths in the browser GUI window, then clicked Run.
For the command line form of the test, I used the command
Here are the first lines of Parsed Artifacts in the Results page in the GUI version
The command line version output the same numbers.
I expected to get more than 0 cache records.
When I looked in hindsight.log I found (snipping out timestamps for brevity)
Steps to reproduce:
Expected results: more than 0 cache records found
Actual results: 0 cache records found, and hindsight.log shows an error
Failed to parse index block file
The text was updated successfully, but these errors were encountered: