933453 - Firefox 24.0 Crash Report [@ EMPTY: no crashing thread identified; corrupt dump ]

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[Tom Sepka]

Attachment: firefox-debug_29ac_2013-10-31_14-00-04-614.log

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Firefox/24.0 (Beta/Release)
Build ID: 20130910160258

Steps to reproduce:

Ran FF in WinDbg, reloaded previous suspect tabs causing the fault.  I suspect it is related to Flashplayer.  Doesn't seem to happen if I set Flashplayer to "ask to activate". rather than "always activate", at least so far....


Actual results:

Seemed to have gotten caught in access violation loop.  Repeatedly tried F5, and then F10 (F10 attempts not part of attached log file).


Expected results:

Other crashes resulted in crash report screen.  I might not have continued hitting F5 enough to get to that point.  I also tried F10, but only after generating the log file as described here:

https://developer.mozilla.org/en-US/docs/How_to_get_a_stacktrace_with_WinDbg

Comment 1

[Tom Sepka]

Attachment: Re-run of faulting sequence of steps without hitting WinDbg F5 to continue.

Comment 3

[Loic]

Are you able to reproduce the crash in safe mode (https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode) and with a clean profile (https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles)?

In addition, provide the list of add-ons/plugins.

Comment 4

[Tom Sepka]

Yes.  See attachment firefox-debug_23b0_2013-11-09_14-20-29-619.log from WinDbg above.  I will provide a list of add-ons and plugins shortly.

Comment 5

[Tom Sepka]

Attachment: firefox-debug_23b0_2013-11-09_14-20-29-619.log (in Safe mode)

Comment 6

[Tom Sepka]

Attachment: Extensions page 1 of 2.jpg

Comment 7

[Tom Sepka]

Attachment: Extensions page 2 of 2.jpg

Comment 8

[Tom Sepka]

Attachment: Plugins page 1 of 2.jpg

Comment 9

[Tom Sepka]

Attachment: Plugins page 2 of 2.jpg

Comment 10

[Tom Sepka]

I have not yet tried a new profile.  I have 3 machines with this problem, and they all have separate profiles.  One is running Windows 7, and the other 2 are running Vista.

Comment 11

[Loic]

They are full of plugins: AVG, Realplayer, Skype etc.. they are good candidates to crash Firefox.

Comment 12

[Tom Sepka]

Attachment firefox-debug_23b0_2013-11-09_14-20-29-619.log was generated in safe mode.  Shouldn't the plugins have been disabled?

I captured the plugins shown in the attachments after restarting FF in normal mode, and not using WinDbg.  I did notice that there was a FF plugin container running when I was in safe mode.  I suspect it was for Flashplayer.

Comment 13

[Tom Sepka]

*** Never mind - I found my own answer that plugins and preferences are not affected in safe mode.***

(In reply to tjsepka from comment #12)
> Attachment firefox-debug_23b0_2013-11-09_14-20-29-619.log was generated in
> safe mode.  Shouldn't the plugins have been disabled?
> 
> I captured the plugins shown in the attachments after restarting FF in
> normal mode, and not using WinDbg.  I did notice that there was a FF plugin
> container running when I was in safe mode.  I suspect it was for Flashplayer.

Comment 14

[Tom Sepka]

Attachment: firefox-debug_1dc4_2013-11-09_23-40-29-461.log, no plugins, safe mode.

Comment 15

[Tom Sepka]

In firefox-debug_1dc4_2013-11-09_23-40-29-461.log,

1.) Set all plugins to "Ask to activate;
2.) Started FF in safe mode in WinDbg;
3.) Opened two previous tabs that have been working properly;  I was not asked to activate, nor did I activate, any plugins.
4.) Opened a tab to ebay.com.  I was not asked to activate, nor did I activate, any plugins.  CPU and memory usage were normal.
5.) Did a search on "i.link" (without the quotes).

CPU usage then maxed out and memory usage kept increasing until WinDbg generated a Break instruction exception.

Comment 16

[Tom Sepka]

Changed version to 25 Branch, as later, similar crashes have followed since about version 22.

Related crash ID's:
ID: 2b61bbe3-2887-426f-9caa-13e6b2131107
ID: ecc96943-61d2-4617-886d-116fb2131107
ID: eddf8bf5-92f6-4fe4-bf4b-d103c2131108
These are crash ID's from version 25.

Also, I believe this crash started after I began blocking site specific media via Tools > Page Info > Media, site specific objects of types Embed and Image.

Comment 17

[Tom Sepka]

Crash became chronic today.

Started FF in WinDbg with -profilemanager in Arguments box.
Selected my profile and chose Work offline and hit Start Firefox.
Hit 2 break points, hit F5 to continue.
Opened my Facebook page (FF is in offline mode).
Opened new tab and navigated to http://webcrosswords.com/daily-crossword-puzzles/ (still in offline mode).
Went to online mode.
Switched to my Facebook tab and hit "try again" and allowed page to completely load.
Switched to http://webcrosswords.com/daily-crossword-puzzles/ tab and hit "Try again".
Selected "Activate Adobe Flash" for the App. and "Allow now" on popup window.
Hit 3 breakpoints in WinDbg and hit F5 3 times to continue at each breakpoint.
Hit reload (page).
Resource monitor showed high CPU usage and memory usage increasing.
Allowed this to continue without interacting with FF.  Resource monitor showed Plugin Container for Firefox suspended and Firefox Not Responding.
WinDbg had hit break point.  Captured log data to file firefox-debug_1f6c_2013-11-22_15-43-09-249.log

Comment 18

[Tom Sepka]

Attachment: firefox-debug_1f6c_2013-11-22_15-43-09-249.log

Comment 19

[Loic]

Could you create a new profile and test with HWA disabled?
http://support.mozilla.org/en-US/kb/forum-response-disable-hardware-acceleration

Comment 20

[Tom Sepka]

I tested with HWA turned off on two different machines, one running Vista and the other running W7.  FF is not sync'd on the machines and they have dissimilar hardware.  I used my existing profile on each machine, and the problem continued.

While I can experiment with a new profile, I've spent considerable time customizing FF with various add-ons. I really don't want to go through that effort again.

I was hoping that by using WinDbg, the root cause of the crash could be identified and corrected.  For me, disabling add-ons and re-enabling them one by one is more of a poke-and-hope method of troubleshooting, and will not determine the root cause of the crash.

Have the log files I have provided given any insight as to where the problem might be?  Is there anything else or more that I can do with WinDbg to find the root cause of the crash?

Comment 21

[Tom Sepka]

Reloaded a previously open tab and after several reloads, FF had high CPU usage, used up almost all memory, and WinDbg encountered a break instruction exception. The WinDbg log file firefox-debug_2b5c_2013-11-24_17-37-26-204.log is attached.

Is any of what I have been uploading here useful?

Comment 22

[Tom Sepka]

Attachment: firefox-debug_2b5c_2013-11-24_17-37-26-204.zip

Comment 23

[Wayne Mery (:wsmwk)]

(In reply to tjsepka from comment #21)
> Reloaded a previously open tab and after several reloads, FF had high CPU
> usage, used up almost all memory, and WinDbg encountered a break instruction
> exception. The WinDbg log file
> firefox-debug_2b5c_2013-11-24_17-37-26-204.log is attached.
> 
> Is any of what I have been uploading here useful?

I think not.  You might try a new profile

Comment 24

[Wayne Mery (:wsmwk)]

(In reply to Wayne Mery (:wsmwk) from comment #23)
> You might try a new profile

Or Help | troubleshooting | reset

Comment 25

[Phoenix]

Resolved per whiteboard