Closed Bug 616117 Opened 14 years ago Closed 12 years ago

Going back to far on the Tumblr dashboard causes Firefox to use excessive amounts of memory and sometimes crash. Empty Crash Reports

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: tech4pwd, Unassigned)

Details

(Keywords: crash, stackwanted, Whiteboard: )

Crash Data

Attachments

(2 files)

Source of page after forcing ram up to over a gig. (contains NSFW images)
272.43 KB, text/plain
Details
Source of page upon load (before auto scolling/paging)
128.35 KB, text/plain
Details 
User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101201 Firefox/4.0b8pre
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101201 Firefox/4.0b8pre

If you go on to the Tumblr dashboard and scroll down, it'll start fetching the other pages (like the auto pager extension does). However, if you go back enough pages, Firefox becomes unresponsive and will eventually crash.

Reproducible: Always

Steps to Reproduce:
1. Open Tumblr Dashboard
2. Scroll down
3. Keep scrolling
Version: unspecified → Trunk
Can you link a relevant CrashID and/or post a Stacktrace?
https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report
Keywords: stackwanted
Oh Noes! This archived report could not be located.

could you try to get another incident id?
I'm no longer getting crashes on this one. Though Minefield does become unresponsive and I'm forced to kill the process.
not loading.. ted?
Well in that case can someone look into what's going on with the crash-stats server. Getting the dashboard to eat memory is easy, getting Firefox to crash rather than stay in a limbo of unresponsiveness isn't as easy and I seldom like doing either.
This is probably just another instance of bug 607810, which means the minidump is empty.
Well bug 607810 was marked fixed on the 11th, my latest crash was on the 17th. Thus there's still clearly an issue.
OK, here we go again, this time I thought I'd copy the report details:
AdapterDeviceID: 2a42
AdapterVendorID: 8086
Add-ons: smartbookmarksbar@remy.juteau:1.4.3,{667e9f3d-0096-4d2b-b171-9a96afbabe20}:1.2.3,{99210d54-6321-41e8-bd1b-2b4c55874efb}:1.16,{a0faa0a4-f1a7-4098-9a74-21efc3a92372}:4.0.1,en-GB@dictionaries.addons.mozilla.org:1.19.1,{1A2D0EC4-75F5-4c91-89C4-3656F6E44B68}:0.4.6,inspector@mozilla.org:2.0.9,testpilot@labs.mozilla.com:1.1,{19503e42-ca3c-4c27-b1e2-9cdb2170ee34}:1.2.8.5,compatibility@addons.mozilla.org:0.8.2,openwebapps@mozillalabs.com:0.1,brief@mozdev.org:1.5.3,{46551EC9-40F0-4e47-8E18-8E5CF550CFB8}:1.1.1,{73a6fe31-595d-460b-a920-fcc0f8843232}:2.1.0.2rc2,{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}:1.3.7a.2964,{972ce4c6-7e08-4474-a285-3208198ce6fd}:4.2a1pre,ffshare@mozilla.org:0.8.2,jid0-NgMDcEu2B88AbzZ6ulHodW9sJzA@jetpack:1.0
AvailableVirtualMemory: 135303168
BuildID: 20110404030429
Comments: Tumblr once again. Can this report please finally go through and give the stacktrace I've so desperately been searching for in order to get this fixed? Please.
CrashTime: 1301939418
EMCheckCompatibility: false
Email: ---
FramePoisonBase: 00000000f0de0000
FramePoisonSize: 65536
InstallTime: 1301928099
Notes: AdapterVendorID: 8086, AdapterDeviceID: 2a42, AdapterDriverVersion: 8.15.10.2202
D3D10 Layers? D3D10 Layers-
D3D9 Layers? D3D9 Layers+
Failed to create temporary texture in system memory. Error code: 2147942414Failed to create temporary texture in system memory. Error code: 2147942414Failed to create temporary texture in system memory. Error code: 2147942414Failed to create temporary texture in system memory. Error code: 2147942414
ProductName: Firefox
ReleaseChannel: nightly
SecondsSinceLastCrash: 541895
StartupTime: 1301930680
SystemMemoryUsePercentage: 94
Theme: classic/1.0
Throttleable: 1
TotalVirtualMemory: 2147352576
URL: wyciwyg://25/http://www.tumblr.com/reblog/4315713675/oATRlzOb?redirect_to=%2Fdashboard%2F85%2F4315729589%3Flite
Vendor: Mozilla
Version: 4.2a1pre
Winsock_LSP: MSAFD Tcpip [TCP/IP] : 2 : 1 :  
 MSAFD Tcpip [UDP/IP] : 2 : 2 : %SystemRoot%\system32\mswsock.dll 
 MSAFD Tcpip [RAW/IP] : 2 : 3 :  
 MSAFD Tcpip [TCP/IPv6] : 2 : 1 : %SystemRoot%\system32\mswsock.dll 
 MSAFD Tcpip [UDP/IPv6] : 2 : 2 :  
 MSAFD Tcpip [RAW/IPv6] : 2 : 3 : %SystemRoot%\system32\mswsock.dll 
 RSVP TCPv6 Service Provider : 2 : 1 :  
 RSVP TCP Service Provider : 2 : 1 : %SystemRoot%\system32\mswsock.dll 
 RSVP UDPv6 Service Provider : 2 : 2 :  
 RSVP UDP Service Provider : 2 : 2 : %SystemRoot%\system32\mswsock.dll 
 MSAFD RfComm [Bluetooth] : 2 : 1 :  
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{40264CF6-04C1-4867-A192-2EC320EE3BE4}] SEQPACKET 2 : 2 : 5 : %SystemRoot%\system32\mswsock.dll 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{40264CF6-04C1-4867-A192-2EC320EE3BE4}] DATAGRAM 2 : 2 : 2 :  
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{4D5441A3-D8C3-4834-9E3C-64CEC2EC73A6}] SEQPACKET 0 : 2 : 5 : %SystemRoot%\system32\mswsock.dll 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{4D5441A3-D8C3-4834-9E3C-64CEC2EC73A6}] DATAGRAM 0 : 2 : 2 :  
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{20D6F566-EC16-4541-8491-C81A2C0890F6}] SEQPACKET 5 : 2 : 5 : %SystemRoot%\system32\mswsock.dll 
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{20D6F566-EC16-4541-8491-C81A2C0890F6}] DATAGRAM 5 : 2 : 2 :  
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{43406AC1-3083-409B-8724-869BBBE22EEA}] SEQPACKET 1 : 2 : 5 : %SystemRoot%\system32\mswsock.dll 
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{43406AC1-3083-409B-8724-869BBBE22EEA}] DATAGRAM 1 : 2 : 2 :  
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{FA22C658-F994-4531-898D-4A5C563C953E}] SEQPACKET 7 : 2 : 5 : %SystemRoot%\system32\mswsock.dll 
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{FA22C658-F994-4531-898D-4A5C563C953E}] DATAGRAM 7 : 2 : 2 :  
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{69F3FEB5-34C2-4290-BF02-6E17867CCD67}] SEQPACKET 6 : 2 : 5 : %SystemRoot%\system32\mswsock.dll 
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{69F3FEB5-34C2-4290-BF02-6E17867CCD67}] DATAGRAM 6 : 2 : 2 :  
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{40264CF6-04C1-4867-A192-2EC320EE3BE4}] SEQPACKET 4 : 2 : 5 : %SystemRoot%\system32\mswsock.dll 
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{40264CF6-04C1-4867-A192-2EC320EE3BE4}] DATAGRAM 4 : 2 : 2 :  
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{4D5441A3-D8C3-4834-9E3C-64CEC2EC73A6}] SEQPACKET 3 : 2 : 5 : %SystemRoot%\system32\mswsock.dll 
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{4D5441A3-D8C3-4834-9E3C-64CEC2EC73A6}] DATAGRAM 3 : 2 : 2 : 

This report also contains technical information about the state of the application when it crashed.

Link: https://crash-stats.mozilla.com/report/pending/38310a62-f88a-43da-9568-7a44f2110404
also including my about:support information. I am crashing on this fairly regular and the usage of tumblr is on the rise:

  Application Basics

        Name
        Firefox

        Version
        6.0a1

        User Agent
        Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110413 Firefox/6.0a1

        Profile Directory

          Open Containing Folder

        Enabled Plugins

          about:plugins

        Build Configuration

          about:buildconfig

  Extensions

        Name

        Version

        Enabled

        ID

        Adblock Plus
        1.3.7a.2969
        true
        {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}

        Add-on Compatibility Reporter
        0.8.3
        true
        compatibility@addons.mozilla.org

        Brief
        1.6b1
        true
        brief@mozdev.org

        British English Dictionary
        1.19.1
        true
        en-GB@dictionaries.addons.mozilla.org

        BugzillaJS
        1.0.1
        true
        jid0-NgMDcEu2B88AbzZ6ulHodW9sJzA@jetpack

        DictionarySearch
        4.0.1
        true
        {a0faa0a4-f1a7-4098-9a74-21efc3a92372}

        DOM Inspector
        2.0.9
        true
        inspector@mozilla.org

        F1 by Mozilla Labs
        0.8.3
        true
        ffshare@mozilla.org

        FlashGot
        1.2.9.2
        true
        {19503e42-ca3c-4c27-b1e2-9cdb2170ee34}

        Image Zoom
        0.4.6
        true
        {1A2D0EC4-75F5-4c91-89C4-3656F6E44B68}

        Mozilla QA Companion
        1.2.3
        true
        {667e9f3d-0096-4d2b-b171-9a96afbabe20}

        NoScript
        2.1.0.2rc6
        true
        {73a6fe31-595d-460b-a920-fcc0f8843232}

        Open Web Apps for Firefox
        0.1
        true
        openwebapps@mozillalabs.com

        Smart Bookmarks Bar
        1.5
        true
        sabret00the@remyjuteau.smartbookmarksbar

        Stylish
        1.1.2b1
        true
        {46551EC9-40F0-4e47-8E18-8E5CF550CFB8}

        Test Pilot
        1.1
        true
        testpilot@labs.mozilla.com

        Tumblr Post
        1.16
        true
        {99210d54-6321-41e8-bd1b-2b4c55874efb}

        Saved Password Editor
        2.0.6
        false
        savedpasswordeditor@daniel.dawson

  Modified Preferences

      Name

      Value

        accessibility.typeaheadfind
        true

        accessibility.typeaheadfind.flashBar
        0

        browser.places.smartBookmarksVersion
        2

        browser.startup.homepage
        about:home

        browser.startup.homepage_override.buildID
        20110413030543

        browser.startup.homepage_override.mstone
        rv:6.0a1

        dom.disable_window_move_resize
        true

        extensions.checkCompatibility
        false

        extensions.checkCompatibility.3.6
        false

        extensions.checkCompatibility.3.6b
        false

        extensions.checkCompatibility.3.6p
        false

        extensions.checkCompatibility.3.6pre
        false

        extensions.checkCompatibility.3.7a
        false

        extensions.checkCompatibility.4.0
        false

        extensions.checkCompatibility.4.0b
        false

        extensions.checkCompatibility.4.0p
        false

        extensions.checkCompatibility.4.0pre
        false

        extensions.checkCompatibility.4.2
        false

        extensions.checkCompatibility.4.2a
        false

        extensions.checkCompatibility.4.2b
        false

        extensions.checkCompatibility.4.2p
        false

        extensions.checkCompatibility.4.2pre
        false

        extensions.checkCompatibility.5.0
        false

        extensions.checkCompatibility.5.0a
        false

        extensions.checkCompatibility.5.0b
        false

        extensions.checkCompatibility.5.0p
        false

        extensions.checkCompatibility.5.0pre
        false

        extensions.checkCompatibility.6.0
        false

        extensions.checkCompatibility.6.0a
        false

        extensions.checkCompatibility.7.0
        false

        extensions.checkCompatibility.7.0a
        false

        extensions.checkCompatibility.8.0
        false

        extensions.checkCompatibility.8.0a
        false

        extensions.lastAppVersion
        6.0a1

        gfx.direct2d.disabled
        true

        layers.accelerate-none
        true

        network.cookie.prefsMigrated
        true

        places.database.lastMaintenance
        1302692232

        places.history.expiration.transient_current_max_pages
        95397

        print.print_printer
        Brother MFC-235C

        privacy.donottrackheader.enabled
        true

        privacy.sanitize.migrateFx3Prefs
        true

        security.warn_viewing_mixed
        false

  Graphics

        Adapter Description
        Mobile Intel(R) 4 Series Express Chipset Family

        Vendor ID
        8086

        Device ID
        2a42

        Adapter RAM
        Unknown

        Adapter Drivers
        igdumdx32 igd10umd32

        Driver Version
        8.15.10.2302

        Driver Date
        2-11-2011

        Direct2D Enabled
        false

        DirectWrite Enabled
        false (6.1.7601.17563, font cache n/a)

        WebGL Renderer
        Google Inc. -- ANGLE -- OpenGL ES 2.0 (ANGLE 0.0.0.611)

        GPU Accelerated Windows
        2/2 Direct3D 9
Severity: normal → major
Why do you think this is related to bug 529733?

Please go to about:crashes and copy the crash IDs here,
it seems the one in comment 5 didn't have any useful info in it.
(In reply to comment #12)
> cc: matspal@gmail.comWhy do you think this is related to bug 529733?
> 
> Please go to about:crashes and copy the crash IDs here,
> it seems the one in comment 5 didn't have any useful info in it.

None of the crash reports appear to resolve. I can make it crash or at least become unresponsive to the point that Windows steps in on demand. That said, I'm not comfortable with installing a Microsoft debugging tool on my system.
why not? you're comfortable running a microsoft operating system.
For the sheer amount of poop that it introduces to my system. MS Visual Studio for example somehow has a ton of files in the root of my drive. And the only reason I have that installed is probably because someone lazily created a dependency on something I installed once.

Ah well. I'm gonna install it. I do feel that this is a major issue that should be fixed.
Is it supposed to be saying that it's unable to verify the checksum of pretty much everything?
windbg is self contained.

and yes, most things don't have checksums.
Finally have a working Crash Report, couldn't get windbg to agree with me. But here we go: https://crash-stats.mozilla.com/report/index/a86a4f9e-70c4-4ccb-9b47-f9e462110429
(In reply to comment #18)
> Finally have a working Crash Report, couldn't get windbg to agree with me. But
> here we go:
> https://crash-stats.mozilla.com/report/index/a86a4f9e-70c4-4ccb-9b47-f9e462110429

That one is empty :-/
can you attach a testcase set of html from the Tumblr url?
Severity: major → critical
Keywords: crash
Summary: Going back to far on the Tumblr dashboard causes Firefox to use excessive amounts of memory and sometimes crash → Going back to far on the Tumblr dashboard causes Firefox to use excessive amounts of memory and sometimes crash. Empty Crash Reports
Same Bug Happen here With FF7 latest beta on Win Xp pro SP3
Do you have the crash report by any chance? go to about:crashes, you should be able to find it there.
(In reply to Paul [sabret00the] from comment #24)
> Do you have the crash report by any chance? go to about:crashes, you should
> be able to find it there.

With the correlation of the bug in about:crashes, I was looking for a solution or somebody that have the same "problem" and I reach this bug Zilla ! ;-)

From some test I've done (Cause FF Crash at least 2 times a day on my work) it may be related in part to the graphic acceleration, so I will buy a new video card soon and comeback to tell the result with the new GPU and more recent driver of course !

FF use almost over 1 gig of memory and slowdown till it crash or I need to kill the process...  and at this time use ~30 percent of the cpu... Always after loading graphics... :(

https://crash-stats.mozilla.com/report/index/bp-8ef5f0e0-75d5-46be-a01d-55b142110901
Still seeing this on 13. What's interesting is that this time I managed to close the tab hoping that it would do the trick but nope.
Paul got bp-77d417bb-1e87-472e-9513-830ec2120410 after "I pressed PgDn probably a couple hundred times."

[@ EMPTY: no crashing thread identified; corrupt dump ]
Status: UNCONFIRMED → NEW
Crash Signature: [@ EMPTY: no crashing thread identified; corrupt dump ]
Ever confirmed: true
Paul, could you try again please for windbg stacktrace? and attach the file to bug.
(In reply to Wayne Mery (:wsmwk) from comment #28)
> Paul, could you try again please for windbg stacktrace? and attach the file
> to bug.

https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg
Flags: needinfo?(sabret00the)
Whiteboard:
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
Found some time to give this a little bit of a play with. Got further than last time, that said, I couldn't do anything in Nightly once WinDbg started it up?
Flags: needinfo?(sabret00the)
Here is a link to my crash report on this problem - https://crash-stats.mozilla.com/report/index/bp-c9fe8b84-dfaf-44a8-8ef5-e32ed2130602 . Unfortunately, it appears to be empty.

Firefox crashed when accessing http://theprincessphotodiary.tumblr.com/ after scrolling down through many pages. Firefox crashed when it's main process (firefox.exe) was using about 2.8 GB of RAM. Before crashing, the Tumblr blog's page turned all white, except for the "Top" image link in the bottom-right corner of the page.

This problem occurs with all Tumblr endless scrolling (infinite scrolling) blogs if the page is scrolled down enough. Sometimes, Firefox will consume over 3 GB of RAM before crashing.

When scrolling through Tumblr endless scrolling pages, Firefox will consume more and more RAM.

This was with Firefox 21.0 running on Windows 7 Home Premium 64-bit. The system has an Intel Core i7 920 CPU and has 9 GB of RAM. However, this same problem occurred with previous versions of Firefox as well.

I have already taken the following steps to resolve the problem:
1. Cleared Firefox's cache.
2. Reset Firefox's profile.
3. Uninstalled all Firefox Add-ons (extensions).
4. Disabled all Firefox plug-ins, except for the latest versions of Adobe Flash and Microsoft Silverlight.
How much free *disk* space do you have left on your main partition? (Trying to find a reason why the crash report is empty / corrupted.)

Can you try to generate a stack trace, as described above?
Oh and may you try to repeat the steps mentioned above with a recent Nightly (http://nightly.mozilla.org/). There have been numerous changes to image handling as well as the graphics layer recently, so the problem might have disappeared in newer versions already.
Unearthing this one as I've been experiencing similar behaviour for months now. It seems consistent because FF crashes ONLY when I have a tumblr tab open, I also experience freezes when I scroll tumblr after I already scrolled a lot down my dashboard.
- When it starts freezing it happens almost every time I hit pagedown or the mouse wheel.
- Un-freezes after a few seconds usually.
- If I leave the tumblr tab alone the rest of the browsing experience is ok, no freezes.
- RAM usage was around 700-800MB when I looked.

https://crash-stats.mozilla.com/report/index/4788a118-94a6-4bef-a93e-6642a2160304
(urls in the report, if any are included, may be NSFW)
Chrome seems to have similar problems...
https://developers.google.com/web/updates/2016/07/infinite-scroller
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: