releasing ip connection (ipconfig /release) crashes firefox (versions 2 & 3) [@ 0x0 - iphlpapi!MapAdapterNameToFriendlyName+0x1b]

RESOLVED INCOMPLETE

Status

()

Core
Networking
--
critical
RESOLVED INCOMPLETE
10 years ago
6 years ago

People

(Reporter: pieter janssens, Unassigned)

Tracking

({crash})

Trunk
x86
Windows XP
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

Attachments

(6 attachments)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4

in windows xp sp1 with ff running as admin or restricted, it crashes when the internet connection is released with the command ipconfig -release of ipconfig /release
this happens also on a fresh profile with no addins.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.


Expected Results:  
not crashing, just reporting loss of connection after a new query.
Type about:crashes and post the crash id please
(Reporter)

Comment 2

10 years ago
Created attachment 312755 [details]
mcr error
(Reporter)

Comment 3

10 years ago
Created attachment 312756 [details]
mcr- tell mozilla
(Reporter)

Comment 4

10 years ago
Created attachment 312757 [details]
ff crash windows event application popup
(Reporter)

Comment 5

10 years ago
about:crashes is empty because the mozilla crash reporter is unable to send the report (the internet connection is restored of course before i confirm to send the report). i've includes several attachments. here are the details which i could retrieve from the mcr:
Add-ons: {972ce4c6-7e08-4474-a285-3208198ce6fd}:2.0
BuildID: 2008030714
CrashTime: 1206983948
InstallTime: 1206794609
ProductName: Firefox
StartupTime: 1206983669
Theme: classic/1.0
URL: 
UserID: bf82c44e-e9bb-4dd4-9995-6eb2c2f5e2b8
Vendor: Mozilla
Version: 3.0b4
(Reporter)

Comment 6

10 years ago
Created attachment 312758 [details]
mcr error

Comment 7

10 years ago
sorry, that's useless, 

http://kb.mozillazine.org/Breakpad explains where the pending folder is
http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg explains how to install and use windbg

install windbg, follow the breakpad instructions to find your pending folder. run windbg, use file>open crash dump and browse to the corresponding .dmp from the pending folder. open that dump. then follow the instructions from the windbg article to get a stack trace. attach the output from windbg here.
Keywords: stackwanted
(Reporter)

Comment 8

10 years ago
sorry i'm not going to install wndbg. i'm attaching the crash dump.
(Reporter)

Comment 9

10 years ago
Created attachment 312768 [details]
crash dump file
(Reporter)

Comment 10

10 years ago
Created attachment 312770 [details]
crash dump extra

Comment 11

10 years ago
0:000> !analyze -v -f
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************

FAULTING_IP: 
+0
00000000 ??              ???

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00000000
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000000
Attempt to read from address 00000000

DEFAULT_BUCKET_ID:  NULL_INSTRUCTION_PTR

PROCESS_NAME:  firefox.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

READ_ADDRESS:  00000000 

FAILED_INSTRUCTION_ADDRESS: 
+0
00000000 ??              ???

LAST_CONTROL_TRANSFER:  from 76d6e268 to 00000000

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
00fdf7d0 76d6e268 00fdfd58 00000000 00fdfc74 0x0
00fdf7ec 76d6fc23 00fdfd58 76d72b28 00fdfc74 iphlpapi!MapAdapterNameToFriendlyName+0x1b
00fdfd70 76d6e9f2 00000019 00fdfdfc 00000000 iphlpapi!AddIPv4InterfaceInfo+0xbf
00fdfd90 76d6fdba 76d6fb64 00fdfdfc 00fdfe08 iphlpapi!ForEachIPv4Interface+0x1a
00fdfe0c 76d6fe42 0000012c 00000000 00fdfe60 iphlpapi!GetAdapterAddresses+0xcb
00fdfe7c 76d69d8a 00000000 00000000 00000000 iphlpapi!GetAdapterAddressesEx+0x26
00fdfe98 607bd68d 00000000 00000000 00000000 iphlpapi!GetAdaptersAddresses+0x5e
00fdfec0 60863032 00000000 000001cc 606e7c69 xul!nsNotifyAddrListener::CheckAdaptersAddresses+0x26 [e:\fx19rel\winnt_5.2_depend\mozilla\netwerk\system\win32\nsnotifyaddrlistener.cpp @ 398]
00fdffb4 77e69ff0 003b7c00 77f517b2 003ce11c xul!nsNotifyAddrListener::CheckLinkStatus+0xb [e:\fx19rel\winnt_5.2_depend\mozilla\netwerk\system\win32\nsnotifyaddrlistener.cpp @ 432]
00fdffec 00000000 60002c60 003b7c00 00000000 kernel32!BaseThreadStart+0x37


STACK_COMMAND:  ~5s; .ecxr ; kb

FAULTING_THREAD:  000000f8

PRIMARY_PROBLEM_CLASS:  NULL_INSTRUCTION_PTR

BUGCHECK_STR:  APPLICATION_FAULT_NULL_INSTRUCTION_PTR

POSSIBLE_INVALID_CONTROL_TRANSFER:  from 76d6e263 to 76d7072a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CPU_CALL_ERROR

FAILURE_BUCKET_ID:  hardware!Unloaded_c0000005_NULL_INSTRUCTION_PTR

Followup: MachineOwner
---------
 *** Possible invalid call from 76d6e263 ( iphlpapi!MapAdapterNameToFriendlyName+0x16 )
 *** Expected target 76d7072a ( iphlpapi!HrLanConnectionNameFromGuidOrPath+0x0 )

Um, I'd contact microsoft. this seems like it's theirs....
Component: General → Networking
Keywords: stackwanted → crash
Product: Firefox → Core
QA Contact: general → networking
Summary: releasing ip connection (ipconfig /release) crashes firefox (versions 2 & 3) → releasing ip connection (ipconfig /release) crashes firefox (versions 2 & 3) [@ 0x0 - iphlpapi!MapAdapterNameToFriendlyName+0x1b]
Version: unspecified → Trunk
(Reporter)

Comment 12

10 years ago
no. they won't fix sp1. and then it could still be a third party network interface driver. thanks for the efforts.

Comment 13

10 years ago
I can re-test this at some point in the future, but I'd be interested in hearing about how we should proceed...

Comment 14

9 years ago
well. someone should contact microsoft, preferably *before* they stop supporting XP.

They should be able to retrieve most information they need from this bug report.
(Assignee)

Updated

7 years ago
Crash Signature: [@ 0x0 - iphlpapi!MapAdapterNameToFriendlyName+0x1b]

Comment 15

6 years ago
Is this still reproducible/actual on XP SP3?
Whiteboard: closeme INCO 2012-09-01

Comment 16

6 years ago
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
Whiteboard: closeme INCO 2012-09-01
You need to log in before you can comment on or make changes to this bug.