Closed Bug 185899 Opened 22 years ago Closed 22 years ago

Mozilla Crashes When Trying to view a Page Source

Categories

(Core Graveyard :: View Source, defect)

Product:
Core Graveyard
Component:
View Source
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: simoesp, Assigned: doronr)

References

(
URL
)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212

the mozilla browser crashes on an atempt to view a source ( i've instaled rpm
build RedHat 8.0 PAckage)

Reproducible: Always

Steps to Reproduce:
1.open a site then
2.View-> PAge Source
3.
Actual Results:  
it Crashes
stacktrace or talkback ID please.

No crash in 2002121708 Linux tar.gz trunk.
to get a stack from the rpm build, you'll need to do
% mozilla
% ps u -C mozilla-bin  (get mozilla's pid)
% gdb /usr/lib/mozilla-1.3a/mozilla-bin _PID_ (or whatever the path is)
(gdb) cont
[get mozilla to crash]
(gdb) bt
[attach the output to this bug]

are you using one of the XFT/gtk2 builds?
Same happens thing happens for me on Windows 2000
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2) Gecko/20021126
OS: Mac OS X.2.3

Until today, view source on mine was working fine.  However, every single time I
have tried doing it today, it has crashed, even after I restarted my system. 
This is happening both in the WWW browser and when reading news.  It would
probably happen in mail as well, but I don't read my mail in Mozilla so I can't
be sure.
Same thing happens with Mozilla 1.3a on OS/2 (Mozilla/5.0 (OS/2; U; Warp 4;en-
US; rv:1.3a) Gecko/20021210).
No crash in trunks OS/2 2003010912 or W32 2003011004. Maybe those of you
crashing should try deleting your XUL file (according to release notes).
i've installed the gentoo disto and mozilla 1.2.1 a now it woks fine for me!
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
The problem's gone away by itself on here.  No doubt it'll come back by itself
at some point in the future....
v
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
Product: SeaMonkey → Core Graveyard
You need to log in before you can comment on or make changes to this bug.