Closed
Bug 264188
Opened 20 years ago
Closed 20 years ago
Crash if I try to view an email
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: thomas-reuss, Assigned: sspitzer)
References
Details
(Keywords: stackwanted)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041013 When I click on an email in one of my mail-Accounts, mozilla crashes with the following output: /opt/mozilla-1.8a4/lib/mozilla-1.8a5/run-mozilla.sh: line 131: 25857 Speicherzugriffsfehler "$prog" ${1+"$@"} I built mozilla on my own with the following configure-Options: ./configure --prefix=/opt/mozilla-1.8a4 --enable-extensions=default,irc,tasks,spellcheck,inspector,venkman,help,typeaheadfind --without-system-nspr --without-system-jpeg --without-system-zlib --without-system-png --without-system-mng --disable-debug --enable-calendar '--enable-optimize=-O3\ -march=athlon-xp\ -mcpu=athlon-xp' --enable-crypto --enable-default-toolkit=gtk2 --enable-xft --disable-freetype2 --disable-xprint --enable-svg -enable-svg-renderer-cairo Reproducible: Always Steps to Reproduce: 1.Build mozilla 2.Start mozilla-mail-client 3.Click on any mail Actual Results: /opt/mozilla-1.8a4/lib/mozilla-1.8a5/run-mozilla.sh: line 131: 25857 Speicherzugriffsfehler (note: german for 'memory access fault') "$prog" ${1+"$@"} Expected Results: mozilla should have showed the selected mail
Comment 1•20 years ago
|
||
Can you give a stacktrace of that crasher (start mozilla with mozilla -g)? You might also want to attach the mail itself.
Comment 2•20 years ago
|
||
-->invalid by mail from reporter: This was caused by Enigmail Extension.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Comment 3•20 years ago
|
||
*** Bug 262773 has been marked as a duplicate of this bug. ***
Keywords: stackwanted
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•