Closed Bug 562016 Opened 15 years ago Closed 12 years ago

Crash on long URL

Categories

(Plugins Graveyard :: McAfee AV, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jpdalbec, Unassigned)

References

Details

(Whiteboard: [Caused by McAfee Site Advisor])

Attachments

(4 files, 2 obsolete files)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 I'll attach an HTML document. Clicking on either link crashes FF 3.6.3. I tried the Google Translate URL from another bug but I don't get a crash there. Reproducible: Always Steps to Reproduce: 1.Open the attached HTML document 2.Click one of the links Actual Results: Program crash Expected Results: Server not found
Attached file HTML document that reproduces crash (deleted) —
wfm with Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.2.4) Gecko/20100413 Firefox/3.6.4 Please read https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report
Attached file Attempt to debug (obsolete) (deleted) —
Disabling McAfee SiteAdvisor seems to prevent the crash. But the debug log seems to point to WOW64?
Attachment #441816 - Attachment mime type: application/octet-stream → text/plain
sorry, the log showed that you didn't quit firefox before trying to start firefox from the debugger. this is because our instructions aren't clear/specific enough about the starting conditions (someone needs to improve them). basically: > 0:000> .tlist this is the command we asked you to run > 0n10556 firefox.exe this is the firefox you already had running before you started windbg > 0n7780 windbg.exe this is the windbg you ran > 0n8612 firefox.exe this is the firefox you asked windbg to debug. unfortunately, this second firefox just looked around, saw the first one, asked it to open a window, and then quit. windbg then told you "the thing you asked me to debug quit". please quit firefox, and try following the instructions again. we really will try to improve the debugging instructions and are sorry for the inconvenience (and given that i'm the unfortunate guy who gets to write the apologies daily at this point, believe me, i'm sorry because the typing hurts my hands).
How do I follow the instructions if Firefox isn't running? Use IE?
print it, save it as text and open it in an text editor or use another browser like IE
Attached file windbg log (obsolete) (deleted) —
Attached file windbg log (deleted) —
Attachment #441816 - Attachment is obsolete: true
Attachment #441857 - Attachment is obsolete: true
Attachment #441860 - Attachment mime type: application/octet-stream → text/plain
ok. the log shows firefox quitting (i think, at least based on "last event", but it wasn't because of a previous instance (good!). i'm not sure why it quit... :( can you please try installing the 32bit version of windbg? that'll reduce the number of variables floating around (debugging firefox using a 64bit debugger is still kinda new to me). i'm very sorry about this.
Attached file windbg log (deleted) —
Attachment #441913 - Attachment mime type: application/octet-stream → text/plain
it seems like something is force quitting the process, i guess. after you enter this: 0:000> sxn gp please execute the following: bp kernel32!ExitProcess "~* kp; g" bp kernel32!ExitThread "~* kp; g" bp kernel32!TerminateProcess "~* kp; g" bp kernel32!TerminateThread "~* kp; g" ...before continuing with the normal stuff. instead of 0:000> bp ntdll!LdrpDoDebuggerBreak+0x30 0:000> bp ntdll!LdrpDoDebuggerBreak+0x2c please do: bp ntdll!LdrpDoDebuggerBreak+0x30 "~* kp; g" bp ntdll!LdrpDoDebuggerBreak+0x2c "~* kp; g"
Attached file windbg log (deleted) —
ok, some of my traps didn't work properly, but the key one did: # 20 Id: be0.135c Suspend: 1 Teb: 7ef7c000 Unfrozen ChildEBP RetAddr 082a8dbc 00000000 kernel32!TerminateProcess so, something is forcefully killing us, i think. there's no stack trace here, which is odd. i'm going to have to think about how to track down who's doing this and how. note that typically terminateprocess wouldn't happen and i certainly wouldn't expect to see it on a thread like 20....
The reporter found that disabling the McAfee SiteAdvisor addon makes this "crash" disappear. Could it be that the McAfee SiteAdvisor backend crashes and the addon quits Firefox for security reasons (no longer protected by the addon) ?
The unloaded module nailite.dll would be part of the McAfee product (NAI=Network Associates, Inc.)
Reporter, is this still happening with 3.6.13 or later? Does disabling the Siteadvisor addon still make the crash go away?
Version: unspecified → 3.6 Branch
Yes to both questions.
Please report to Macaffe then, the siteadvisor is a binary addon and is the issue behind the crash here.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Component: General → Extension Compatibility
Depends on: 637542
QA Contact: general → extension.compatibility
Whiteboard: [Caused by McAfee Site Advisor]
McAfee are working on an updated version of their Site Advisor extension, to prevent the issues it causes with Firefox. To help work out what versions of the extension don't work (for the purposes of blocklisting it in bug 637542), it would be useful to know what version you are using. Please can you go to the page "about:support" (type it without quotes in the address bar) and paste the contents of the extension section as a reply here. Thanks! (Filter bugmail on mcafeeblocklistspam)
McAfee SiteAdvisor Enterprise 3.0.0.539 true {B7082FAA-CB62-4872-9106-E42DD88EDE45} Tab Mix Plus 0.3.8.4 true {dc572301-7619-498c-a57d-39143191b318} Live HTTP headers 0.16 true {8f8fe09b-0bd3-4470-bc1b-8cad42b8203a} Firebug 1.6.2 true firebug@software.joehewitt.com Java Console 6.0.13 true {CAFEEFAC-0016-0000-0013-ABCDEFFEDCBA} Java Console 5.0.22 true {CAFEEFAC-0015-0000-0022-ABCDEFFEDCBA} Nightly Tester Tools 3.1 true {8620c15f-30dc-4dba-a131-7c5d20cf4a29} HTTPS-Everywhere 0.9.4 true https-everywhere@eff.org WAVE Toolbar 1.1.5 true wavetoolbar@webaim.org
thanks for posting the information. I hope we can blocklist this addon from Firefox4
Reopening since now in the McAfee section, so something for them to sort out.
Status: RESOLVED → UNCONFIRMED
Component: Extension Compatibility → McAfee AV
Product: Firefox → Plugins
QA Contact: extension.compatibility → mcafee-antivirus
Resolution: INVALID → ---
Version: 3.6 Branch → 3.x
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: