399557 - Visual Studio 2005 debugger is launched upon closing browser while viewing website

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Jose Hernandez]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8) Gecko/2007091216 GranParadiso/3.0a8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8) Gecko/2007091216 GranParadiso/3.0a8

When I visit the website www.scout.com and close Firefox the Visual Studio 2005 (VC8) debugger is launched. The debugger states "An unhandleld win32 exception occurred in firefox.exe [2668].". When I tell it to debug it brings me to Visual Studio 2005 and a pop up says "Unhandled exception at 0x7c918fea in firefox.exe: 0xC0000005: Access violation writing location 0x00000010". Afterwards it brings me to a locked file named free.c and breaks in line 115.

Reproducible: Always

Steps to Reproduce:
1. Visit www.scout.com
2. Close Firefox
Actual Results:  
The Visual Studio 2005 debugger is launched.

Expected Results:  
Not have the Visual Studio debugger launch (because there is no unhandled error).

Comment 1

[Andy]

When I had visual studio installed I would randomly get the visual studio 2005 debugger dialog popup. It would not always happen on any particular page. It seemed random. I now have visual studio un-installed and now I get this error message box popup whenever I close a firefox window:

An unhandled win32 exception occurred in firefox.exe [2408]. Just-In-Time debugging this exception failed with the following error: No installed debugger has Just-In-Time debugging enabled. In Visual Studio, Just-In-Time debugging can be enabled from Tools/Options/Debugging/Just-In-Time.

Visual studio is not even installed. Why is it looking for visual studio debugger?

Comment 2

[Frank Wein [:mcsmurf]]

Jose: Can you send in a Breakpad crash report (see http://kb.mozillazine.org/Breakpad) with a current trunk build and write down the Breakpad ID in the bug here?

Comment 3

[Tyler Downer [He/Him]]

Does this still happen in firefox 3.6.6 or later in a fresh profile?

Comment 4

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.

Comment 5

[Andy]

Don't see this problem anymore. please close this bug. Using 3.5 something. This was orignally posted in 2007. Kind of slow in responding I would say.