Closed Bug 190342 Opened 23 years ago Closed 22 years ago

enigmail crashes composer 1.3a due to multiple enigmail overlapping installs

Categories

(MailNews Core :: Composition, defect)

x86
Windows 98
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: galen, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021212 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021212 Mozilla 1.3a had fatal memory leak when saving / sending e-mail with enigmail installed. Enigmail had two [unwanted] installs running 0.71.3 and 0.72.0 Solved by uninstall of enigmail and removal of file chrome/enigimail.jar Fatal memory leak would require a quick application kill via C-A-D or hard boot if left to drain resources. Reported to enigmail newsgroup Reproducible: Always Steps to Reproduce: 1. compose & save / send e-mail 2. 3. Actual Results: mozilla becaome frozen and memory drained away Expected Results: sent / saved e-mail Just hoping this info will help others debug
I'm pretty sure this is a dup of other enigmail related crashes seen with Mozilla 1.3 Alpha and recent MozillaTrunk builds. I will look up those bugs and update later.
Reporter, do you still see this problem with the latest nightly? If not, this bug can be closed. Thanks.
no longer user 1.3a
Reporter, could you elaborate? Is it that: 1) you are using a later version of Mozilla with enigmail and it works fine, OR 2) you are not using mozilla with enigmail at all? Thanks.
Reporter, can you try a newer build of enigmail and mozilla? The newest build of enigmail is 0.82.1
Reporter, is this still a problem with current versions of Mozilla & Enigmail?
That was an old bug of enigmail, before it was properly adapted to Mozilla 1.3a. I suggest to mark it WFM.
Oh, today is my Enigmail bug hunting day ;-)))) Marking WFM
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.