browseback - 1.5web history visualization and search tool |
|
||||||||||||||||
|
|||||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews
Troubleshooting
Usage Tips
Developer Notes
Commentary
Featured Reviews
This is crap 



- Version: 1.4.2, 2/1/2008 12:00AM PST
(0 of 1 users found this comment useful)
salala98
I tried browseback 2 times and both times it crashed immediately. Useless.
This is crap 



- Version: 1.4.2, 2/1/2008 12:00AM PST
(0 of 1 users found this comment useful)
salala98
I tried browseback 2 times and both times it crashed immediately. Useless.
As with many others who've commented, Browseback, while a great idea in theory takes up a great deal of CPU and memory, especially while it's scanning in the background. While trying to adjust the preferences, it's crashed on me several times. However, what irks me the most about Browseback is that the options in the preferences window for how much disk space its cache should take up, how long it should retain its history, and from what date it should start importing simply aren't respected at all by Browseback. They'd might as well not be there at all.
After setting it to use 50 MB of disk space, I've consistently seen its disk cache balloon to over three times that, thanks to entries dating back from December 2007 which it won't delete even though I told it to only keep entries for two days, starting from yesterday. I ended up just deleting it manually. This was an issue I had with it when I started using it at 1.4 and it's still behaviour I see now in 1.5.