Hi bauermusic,

Bugs need to be confirmed by others and even then they need to be prioritised. If it is thought that all you are reporting is a problem with a single specific site then it is not a Firefox issue and unfortunately the bug may be left without any attention.

Filing bugs is not really a user friendly experience and often does not resolve support issues.

Before going any further with the bug you have filed it may be worth trying Firefox 28 as that has fixed a memory bug in Firefox on Macs. If you are lucky it may be the same issue.

• Firefox 28 is available from the Beta channel
  http://www.mozilla.org/en-US/firefox/channel/#beta/beta-desktop
• Instructions on using an additional install see http://kb.mozillazine.org/Testing_pre-release_versions#Installing_multiple_versions

You cleared the original info in your post of today's date with a note

-- (Sorry, cannot delete) --  

so I will delete that post for you.

I do not use a Mac myself so I am not able to help directly, but try Firefox 28 and if that fails to resolve this mention other sites that cause the problem, preferably well known and public ones and I will see if I can interest someone else in helping.

Note about:memory results will almost certainly be useful see for instance this thread

• Firefox on OS X 10.9.1 still has huge memory leak (/questions/981674) /questions/987722

Thank you, appreciate the time.

I agree that a 'one misbehaving site' is not an issue. My point was that FF should not allow 'A site' to breach system memory(?). Or/and the 'Tab Page' was leaking. But I could be dead wrong about it.

<strike>I can (try to) debug a Javascript, but this issue is out of my spectrum. (I have no idea where to even stick a break-point.)</strike>

I'll try to have a look myself, I realized FF can't debug itself (dah!), and running it from Xcode (that would be the developer tool for Mac) is simpler than I thought. I'll have a go at it.

Thanks again!

No time right now but two quick comments

• Try to use about:memory to demonstrate memory use keeps increasing, and test whether the option in about:memory to reduce memory use has any effect ?
• Try to identify another site that has a similar problem.

Also as I mentioned in the last post test Firefox 28, the problem may have already been solved in Firefox 28.

Firefox does have its own built in tools,including java console and profiler.

I know Firefox's Web Console, as well as Firebug. Problem is, well:

1. Nothing (no Javascript) is running on 'Tab Page'.

2. This sucker freezes the whole system in 15 seconds.

So, I can't really stop it and go step by step to pin point the issue. Regarding 'about:memory', I'll have to click it within the 15 seconds window before it all goes dark. Once this thing starts, the only way to stop it is quitting Firefox. I'll give Firefox 28 a shot.

I am able to open the page from the link you mention https://parse.com/ without crashing, but I do not use OS X

If it is a website able to break Firefox it is well outside my area of knowledge but no doubt you will be able to study the site and produce a reduced test case demonstrating the issue.

Does using the profiler help you ?
That will enable you to study the detail in snapshots of a few seconds.

• https://developer.mozilla.org/en-US/docs/Tools/Profiler

If no one with knowledge of this sort of issue jumps in you could try the Mozillazine forum

• http://forums.mozillazine.org/viewforum.php?f=25

"I am able to open the page from the link you mention https://parse.com/ without crashing, but I do not use OS X"

The problem is not opening the site. That works just fine. The problem is when that site sits as one of the thumbs in the 'Tab Page'.

I just mentioned the steps to get that thumb into 'Tab page' (since this is done automatically ), I only meant to explain how to do so manually.

In short, this is all about 'Tab Page' misbehaving, not 'a site'.

IF, when you open a new tab, you can see 'parse.com' as one of the thumbs and nothing happens (for a minute or two), then this might be just a Mac issue. (I'll have a chance to test it on Windows next week).

Sorry I do not quite understand this.
Is the problem only the OS X Activity Monitor and that is causing the computer to freeze.

Do I understand correctly you saying the problem is not with Firefox and the site itself.
The problem only occurs when you use the OS X activity monitor and that crashes and memory problems only occur with the activity monitor open and something is dragged into the activity monitor 'Tab Page'

Presumably if the activity monitor is only reporting the situation then the memory increase and crash would be expected to occur with Firefox regardless of whether the activity monitor is open and in use, otherwise the issue is the atcivity monitor itself.

Forget about Activity Monitor. Just replace the words "Activity Monitor" with the words "Tab Page".

Activity Monitor is just a tool to show the computer's memory.

"open and something is dragged into the activity monitor 'Tab Page'"

NO! Dragged into FIREFOX Tab-Page. As in:

http://www.extremetech.com/wp-content/uploads/2012/06/firefox-13-new-tab-page.jpg

Go to https://parse.com/ and drag a shortcut to Firefox-Tab-Page. (See picture). It has small icons of websites. To add a site to that page, you drag from the address bar (of say, https://parse.com/) https://parse.com/ ) to that page (in the picture).

_{fixed link - trailing bracket needs a space before it ~J99}

Hi again,

Just having a coffee break and using someone else's account on a Windows machine.

No problem seen on that. Note the new tab page may be opened using the about protocol & navigating to about:newtab and that besides dragging bookmarks or shortcuts the pinned thumbnails may be set from about:config the preference is

browser.newtabpage.pinned

and the string value now includes

[{"url":"https://parse.com/","title":"Parse"},   

I am going out now but will find time later today to also try this in Firefox on Linux.

You're right on the money now! Awesome. +1

OK something is very weird. I am seeing unexplained behaviour on Linux (Ubuntu).
I will see if I can look into this further next week.

Have you only noticed this issue with this one site, or do you see it with other sites ?
If so can you give another couple of examples where this is noticed.

So far, that site alone. There could be others, but it's hard to tell what's causing this without looking more deeply. I'm just glad I was able to reproduce this.

I tried the About:Memory thing, and tried doing the "minimize memory usage", and the GC & CC buttons, and it did nothing but change my FF memory usage from 2.7 GB, to 2.79GB! (it's lately been shooting up to 6, 7, or even 8GBs...

And when I did the Show Memory Report, and hit Measure, this is what I got:

WARNING: the following values are negative or unreasonably large.

   gfx-surface-quartz 

This indicates a defect in one or more memory reporters. The invalid values are highlighted.

Now, I have no idea what that means, any ideas?

And since I'm on a Mac, too, and suffering from high memory usage, should I try FF28?

Is there any way to save all my currently opened tabs so that I can re-open them should I go to the beta version, and something screws up? I wish, like Safari, & Chrome, the re-opened windows & tabs would be listed in the history, each time I open the browser, as then it's easy to simply highlight & copy them to a list of links... Where does FF hold the memory of open tabs, it is in some other file?

@StevenCee - I'm not sure we're talking about the same problem. My issue is the "Tab Page", where you open a new tab and get a thumbnails window with (most visited?) sites. In that page, there is a specific site-thumb that cause problem.

I have Firefox on around 200MB, IF the site "parse.com" is on that "Tab Page", the minute I open a new tab the memory shoots from 200MB to 1.8GB (out of 2GB), which cause the whole OS X to become unresponsive (which should never happen).

So far, I know only of the "parse.com" specifically, I have other links (YouTube, Facebook and others) on "Tab Page" that are fine.

Also, I tested Firefox 28 and this problem effect 28 as well.