bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

click in firefox.exe - crash

RESOLVED INVALID

Status

()

Firefox
General
RESOLVED INVALID
12 years ago
12 years ago

People

(Reporter: daikatana, Unassigned)

Tracking

({crash})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [sg:needinfo])

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5

FIREFOX spowodowa³ ogólny b³±d ochrony
w module USER.EXE przy 0004:00001e66.
Rejestry:
EAX=00004bb0 CS=17c7 EIP=00001e66 EFLGS=00000202
EBX=17df0000 SS=41e7 ESP=00008a8a EBP=00008a9c
ECX=000279c0 DS=16d7 ESI=000079c0 FS=0faf
EDX=817a0040 ES=53cf EDI=000001b8 GS=0000
Bajtów w CS:EIP:
c4 5e 08 26 39 47 16 74 34 83 7e 06 00 75 0f c4 
Stos:
01b80000 6d2a0000 000017cf 000153cf 8ae80000 00001c00 00000000 0000438f 000053cf 0000c4fa 04c80500 000288ec 01b802e0 00000000 8ad80000 9b4341e7 


Reproducible: Always
Click where? on what?  You say reproducable "Always", but I click on tons of things without crashing.

We need much more specific steps on how to reproduce in order to fix it, or a stack trace that might give us a clue which Firefox routines are involved (USER.EXE is a standard windows library. We're probably passing bad stuff, but the crash address doesn't offer much of a clue what).

A talkback report would be a good way to get a stack trace in a useful searchable format. See http://kb.mozillazine.org/Talkback
Keywords: crash
Summary: click in firefox.exe - bug → click in firefox.exe - crash
Whiteboard: [sg:needinfo]
Not enough info... hopefully we'll catch this crash from data supplied by other users.
Group: security
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.