Browser's Back button loses history
Recently TenFourFox seems to lose the history on the Back button. For example, I was browsing Cisco's web site about our router, and every time I went to a specific article I could only go back one page - then the Back button would gray out. The pages are still storied in the History menu, but the Back button can't seem to find them.
Is there a fix?
TenFourFox 38.5.0 on OS 10.4.11, PowerBook G4
Thanks.
- Winston
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Cameron Kaiser on 19 Jan, 2016 05:13 PM
I can't replicate this -- the back history button appears fine here. Is it only on that Cisco page, or every single page you visit?
2 Posted by Winston on 19 Jan, 2016 05:37 PM
It's happening right now on Dropbox. I can only go back one page - any others that should be in the "back button" history aren't there.
Thanks.
- Winston Weinmann
Cameron Kaiser wrote:
Support Staff 3 Posted by Cameron Kaiser on 19 Jan, 2016 05:43 PM
This sounds like an add-on causing problems or a stuck setting. None of the test systems here do that. Have you looked at a profile reset as a next step? (See "How to reset your profile" at the bottom right.)
4 Posted by Winston on 19 Jan, 2016 05:52 PM
I'll try a profile reset. Thanks.
- Winston Weinmann
Cameron Kaiser wrote:
5 Posted by Winston on 19 Jan, 2016 05:55 PM
ps. Will have to do it later - maybe tomorrow am, as I don't have time right now.
Thanks.
Cameron Kaiser wrote:
6 Posted by Winston on 20 Jan, 2016 09:04 PM
Cameron -
My only-back-one-page was caused by installing Atlemose's compilation of eyoungren's TenFourFox tweaks. I've gotten an explanation of how to fix it, so all is good now.
Still having problems with TFF crashing when I try to fill in a form. Latest was clicking on the Subject line in a Cisco Registered Envelope Service email. The good news is that it never seems to happen twice in a row, so once TFF is reopened I've been able to complete the form in question.
Best,
- Winston
Cameron Kaiser wrote:
Support Staff 7 Posted by Cameron Kaiser on 20 Jan, 2016 09:12 PM
Unfortunately, something that intermittent will be quite difficult to investigate. If you find a site on which it occurs consistently, please post the URL (it should be publicly accessible).
8 Posted by Winston on 21 Jan, 2016 12:38 AM
If I go to pretty much any product on Amazon, then click on "Comments" for a review of that product, then click on "Comment", TenFourFox crashes.
For example:
<http://www.amazon.com/gp/product/B00CHHU3Q0/>
Scroll down to "Customer Reviews".
First review says "2 Comments". I click on that.
Page opens with "Add a Comment" at top.
When I click on "Add a Comment" TFF crashes.
If I go back to the same page after I reopen TFF, and repeat, TFF does not crash.
Then I go back to the product page and click on the first alternative lantern:
<http://www.amazon.com/dp/B00S70O3U8?psc=1>
I scroll down to the first review, and click "Comment"
No crash.
So I go to a Cisco Registered Envelope that I have in History. No crash.
Then when I go back to the second Amazon product page from History and click on "Comment" TFF crashes.
Not quite replicable each time, but not far from it.
Thanks.
- Winston Weinmann
Cameron Kaiser wrote:
9 Posted by Winston on 21 Jan, 2016 12:41 AM
ps: Cisco's Registered Envelope Service is here:
<https://res.cisco.com/websafe/root>
If you need access to it, give me an email address and I'll send you a message from that service so you can register.
Thanks.
- Winston
Winston Weinmann wrote:
Support Staff 10 Posted by Chris (chtrusch... on 21 Jan, 2016 06:33 AM
I can't reproduce the "Add a Comment" crash at all.
11 Posted by Winston on 21 Jan, 2016 02:25 PM
OK. When I have time I'll try doing a full reset and see if that helps.
Thanks for checking on it.
- Winston Weinmann
Chris (chtrusch) wrote:
Support Staff 12 Posted by Cameron Kaiser on 21 Jan, 2016 03:56 PM
I tried a few different combinations of clicking on items and comments and I can't reproduce it either on the G5 or this iMac G4. Perhaps one of the custom settings is enabling a buggy code path we don't normally test?
13 Posted by Winston on 21 Jan, 2016 04:03 PM
The problem is that this has been happening for several months, long before I added the custom settings. Could it have something to do with an add-on? I can try disabling some of them to see if that's the source.
When I get a chance I'll also try doing a full reset to see if that fixes things.
Thanks for looking into this.
Best,
- Winston
Cameron Kaiser wrote:
14 Posted by Winston on 22 Jan, 2016 02:05 PM
I disabled all my add-ons and that did not fix the problem of TenFourFox crashing when I click into a comments field. I disabled them all, and then went to "Comment" on a randomly chosen item on Amazon, and got a crash as soon as I clicked into the Comment box.
Reset is next.
- Winston Weinmann
Cameron Kaiser wrote:
15 Posted by Winston on 22 Jan, 2016 02:17 PM
Cameron -
Minor item, but it may confuse some folk: The link on the support page says "How to reset your profile", and the instructions page is titled that, and says
"Go to Help, Troubleshooting Information. A new page will open.
Click on the Reset TenFourFox button."
But the button says:
Give TenFourFox a tune up
Refresh TenFourFox . . . "
"Refresh" instead of "Reset."
Thanks.
- Winston Weinmann
Cameron Kaiser wrote:
16 Posted by Winston on 22 Jan, 2016 02:27 PM
Reset, without re-adding add-ons or the tweaks, did not fix the problem with TenFourFox crashing when I click on a "Comment" box on Amazon. Crashed again as soon as I tried it. The only change I'd made after the reset was to set the home page and search choice to DuckDuckGo. No other changes made to the stock setup.
As this seems to happen with text entry boxes on a number of web sites, I assume it has something to do with how TFF interprets a text entry box.
As I mentioned, the problem pre-dated installing the tweaks.
- Winston Weinmann
Cameron Kaiser wrote:
Support Staff 17 Posted by Cameron Kaiser on 22 Jan, 2016 02:44 PM
I'll make those changes, but I still can't reproduce the problem. Without a reliable test case I can't do much further analysis. How much memory is in your computer?
The only other suggestion I have is another user reported something similar with a different site a few months ago that we couldn't replicate either (another crash bug was identified during its investigation that we could replicate, but it wasn't the problem he was having). Perhaps you could see if there is something about your systems that you have in common.
http://tenfourfox.tenderapp.com/discussions/problems/7029-crashing-...
18 Posted by Winston on 22 Jan, 2016 03:06 PM
I'm on a 12" PowerBook G4 1.5 GHz with 1.25 GB of memory, running OS 10.4.11. I also have an OWC SSD installed. I try to keep a minimum of programs open at one time, and regularly monitor memory with Activity Monitor. However, with just a small complement of programs open, I still run close to being out of memory, which is why I restart TFF regularly. For example, just opened TFF is taking 220 MB.
I'll take a look at the thread you suggested.
Thanks.
- Winston Weinmann
Cameron Kaiser wrote:
19 Posted by Winston on 22 Jan, 2016 03:23 PM
Cameron -
I'd read the thread you linked to previously when I was researching this. It sounds like the same issue I am having. I've posted my system's specs on that thread.
- Winston
Cameron Kaiser wrote:
Support Staff 20 Posted by Cameron Kaiser on 23 Jan, 2016 01:09 AM
Believe it or not, that's about right. Just
mmap()
ing XUL, the major superlibrary that contains most of Firefox/TenFourFox, is good for 70MB or so, and that's before you've loaded any of the browser chrome, let alone pages. My 1GHz iMac G4 has exactly the same amount of memory your PowerBook has and I don't routinely need to restart the browser, but YMMV, of course. In Activity Monitor it's showing about 300MB of physical memory and about 1.5GB of virtual memory.So I don't think low memory is the problem here, since this iMac G4 has a weaker configuration than yours.