|User since||April 18, 2008|
|Number of add-ons developed||0 add-ons|
|Average rating of developer's add-ons||Not yet rated|
reducing memory consumption (yet again) Rated 3 out of 5 stars
In reply to the dev, yet again:
This will be my last post as I fear you may not stop replying otherwise. Some information in your replies is misleading.
You seem to go back and forth between "it does save memory" and "it doesn't save memory".
40 or even 20 tabs from the same website is hardly a "fair representation" of typical browsing behavior. If one needs such unrealistic scenarios and on top of that must also wait several minutes to get any tangible memory savings then that's not very useful.
Typical browsing behavior means diverse tabs from different websites, and I already documented in my 1st review the "memory savings" of OneTab in such a scenario in my case (obviously, your mileage may vary): 22 tabs, 500 MB, then 480 MB immediately after OneTab collected them ... so 20 / 500 MB, or 4% memory savings. Maybe that would have increased to 40 or 50 MB after several minutes, I didn't wait (when I need to save memory, I do because I'm running out of it elsewhere, so it should be quick)
For me that's hardly useful as a memory saving tool. But sure, if you save 20 MB or even 50 MB out of 500 MB after several minutes then you can rightfully claim you are saving memory. Even 1 MB saved would do. Who am I to argue?
Good luck with everything.
p.s. Like I said, I still use your extension in Chrome where I find it quite useful. On Firefox for me it's only useful as a tab collector, not as a memory saving tool.
reducing memory consumption (again) Rated 3 out of 5 stars
In reply to the developer (again):
1. you said you don't claim to reduce memory consumption in firefox, but that is (pretty brutally) contradicted by the very title of your firefox add-on which says "OneTab - Too many tabs? Convert tabs to a list and reduce browser memory" ... this addon does not reduce the memory usage of firefox (at least not yet)
2. I never mentioned about:memory in my review, but task manager. That's the accurate way to investigate memory usage (free memory before and after).
3. your test using youtube tabs is very misleading because youtube uses html5 video or the flash plugin, which is a separate process (executable) forked by firefox.
You're getting criticism because you made two claims that are untrue (one in the add-on title, one in the reply here). Feel free to fight back, but that won't change the reality. You may want to change the title though.
I still use your extension in Chrome, and am grateful for it, don't get me wrong.
reducing memory consumption Rated 3 out of 5 stars
The developer replied to my previous review (https://addons.mozilla.org/en-US/firefox/addon/onetab/reviews/user:1131364), which I appreciate, also gives something to look forward to.
The dev said "You'll notice we don't make the memory claim in the Firefox store page" but the very title of your Firefox add-on page says "OneTab - Too many tabs? Convert tabs to a list and reduce browser memory". Quite some contradiction.
That being said, I look forward to seeing memory being reduced in Firefox too.
nice, but doesn't really reduce memory consumption Rated 3 out of 5 stars
It does collect all tabs into one page listing, but it does not reduce memory footprint. If you don't believe me then open 20 tabs or so, and monitor the allocated/free memory with Task Manager before and after collecting them all into OneTab.
With 22 tabs open my Firefox is at about 500 MB. Pressing the OneTab button and collecting them all into OneTab reduces that to about 480 MB ... hardly any reducrtion. However, restarting Firefox with just the OneTab tab gives 250 MB.
Simply put, reducing memory does not work in Firefox.
It does work in Chrome though (try it). There the memory consumption is reduced dramatically when pressing the OneTab button.
auto-hide not working in FF 38.0.5 Rated 3 out of 5 stars
auto-hide is no longer working in FF 38.0.5This review is for a previous version of the add-on (184.108.40.206-signed).
Rated 3 out of 5 stars
On MacOSX (FF 37.0.2) it does nothing, unfortunately. I used to use this in Windows where I remember it worked.
Great! Would be better if overlayed over page! Rated 4 out of 5 stars
After hassling with the Roomy Bookmarks Toolbar (RBT) add-on which is buggy, I came back to this. I use the mouse activation method over a toolbar (so essentially all the top part of Firefox). The reason I was trying RBT is that it could display the toolbar overlaid on the page, instead of bumping the page down to insert the toolbar. This way you don't bump the page up and down when you move the mouse into/out of the upper side of Firefox -- it gets annoying when you come back to the page and want to click a link or input box and the page bumps back up, messing your aim ...
Would you consider adding this feature?
Great addon ... no longer works on FF26+ and Win8.1 Rated 5 out of 5 stars
Still gave it 5 stars as it was so useful until now ... has been broken ever since FF26 though. Please bring it back to life.This review is for a previous version of the add-on (220.127.116.11-signed). This user has 2 previous reviews of this add-on.
Auto-deletion Rated 4 out of 5 stars
I left a review earlier and you (the dev) replied, thanks - but I can't reply to that. You said files are auto-deleted after a while, and that there is a hidden option for specifying a download folder (sorry for missing that info in the description). But if I set another folder, I most likely do *not* want files to be automatically deleted ... certainly not other files in that folder that were not downloaded via this add-on. Is that the case or not?p.s. If there is a proper user forum for discussing such issues then I apologise for not finding it.This review is for a previous version of the add-on (18.104.22.168-signed). This user has other reviews of this add-on.
Great add-on, could use an option though Rated 4 out of 5 stars
I've been using this for a long while, nice add-on!
It's missing two options:
1) delete file after execution
2) specify the download directory before execution. Right now it's in "%TEMP%\mozOpenDownload" which is not always what i want.
For instance, I'd prefer most of them to go in my usual downloads folder so I keep them afterwards, rather than having to navigate to "C:\Users\MyName\AppData\Local\Temp\mozOpenDownload" and move it from there ...
Doesn't work properly in v14b and v15a Rated 2 out of 5 stars
I manually placed the "Report" icon on the toolbar. Pressing it while selecting a message it says "No message are marked as Junk in the current folder".
Marking a message as Junk moves it into the Junk folder. If I use the "Report" button while in the "Junk" folder, it doesn't do anything. If I move a junk-marked message back to inbox so that I can use the report button (very convoluted) then it pauses for half a second and then nothing. I don't see any confirmation, I'm not sure it did report anything. I did so with 20 junk messages and it spent just as much time in that "pause" state as it did when there was only 1 junk marked message. Looks suspicious.
This extension should work on the messages that are highlighted (too), rather than only on those marked as junk; it should mark as junk at the same time to save clicks or awkward maneuvers (having to get all massages from junk into inbox and use the button again).
Rated 4 out of 5 stars
However, in TB 11, 12 and 13 beta (right now using the latter), clicking options and unchecking or checking more folders to always show makes no difference. My changes are not remembered at all! I can't give 5 stars because of this problem.
Can you please fix this?
Rated 3 out of 5 stars
Has this been tested on FF v7? It doesn't complain when installed but it appears to do absolutely nothing to the memory ... waiting for it to unload all tabs (about 60 of them) leaves the memory completely unchanged (around 450 MB).This review is for a previous version of the add-on (1.0.1-signed.1-signed).
Rated 4 out of 5 stars
Tanks for the update. I'm missing the "unload tab after ... n hours" feature ... will that be implemented in TabBar Lite?This review is for a previous version of the add-on (1.1.1-signed.1-signed).
Correct workaround for FF 3.6 Rated 4 out of 5 stars
for all people who want to make this work in FF 3.6, see my workaround below which works
don't bother trying to edit install.rdf, that won't work
Rated 4 out of 5 stars
People should just stop suggesting to edit install.rdf ... it just doesn't work.
You have to first disable extension compatibility checking in FF v3.6. This is different than in all previous versions. You have to add the following boolean value and set it to false in the advanced config editor: "extensions.checkCompatibility.3.6".
1. type "about:config" in the URL text box and choose "yes" to the "are you sure" prompt
2. Right click any white space and choose "New" > "Boolean"
3. Type or copy/paste "extensions.checkCompatibility.3.6" (without the quotes)
3. Choose "false" as the value
4. Restart FF
More details (including future FF versions) here:
The author should do the needful and update this extension nonetheless.
Doesn't work in 3.6 RC2 Rated 4 out of 5 stars
It doesn't work in 3.6 RC2 ... even if you disable the compatibility checker or edit install.rdf to modify the max version. Hopefully the author will update it, I'm pretty dependent on this extension as well.
Be careful! Rated 2 out of 5 stars
This extensions can be dangerous since it caches content that was not supposed to be cached, such as online banking details as the user before me was so happy about or other private info.
Do not have your browser cache your bank account pages!!!
Such information being left in the cache can then be much easier used by malicious users since they only need to get access to the browser's cache which in most cases are just files. Those are in many cases much easier to get than sniffing out ssl tunneled communication info ... there is a reason why such pages are supposed NOT to be cached.
It can be a cute extension too though, getting files (e.g. images, flash videos) that otherwise were fetched and displayed.