If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Eudora crashes on launch after OS X 10.6.4 update.

RESOLVED INCOMPLETE

Status

Penelope
General
--
critical
RESOLVED INCOMPLETE
7 years ago
7 years ago

People

(Reporter: Martin, Assigned: Matt Dudziak)

Tracking

({crash})

Details

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Eudora-8.0b9.en-US.mac.dmg downloaded today 

I updated OSX to 10.6.4

Eudora crashes on startup. I downloaded latest Eudora. 8.0b9 crashes on startup. I deleted all the mail folders, but connection to server downloaded new mail, still crashes on startup

Reproducible: Always

Steps to Reproduce:
1.Launch Eudora
2. That's it! (note OSX 10.6.4 update).
3.
Actual Results:  
crash and crash logging starts
can you provide a crashID please ? (see http://support.mozillamessaging.com/en-US/kb/Mozilla+Crash+Reporter)
Assignee: nobody → mozilla-bugs
Component: General → General
Keywords: crash
Product: Thunderbird → Penelope
QA Contact: general → general
(Assignee)

Updated

7 years ago
Duplicate of this bug: 588707
very likely Bug 593132 - Mac crash sorting on subject or on startup [@ UCGetCollationKey] sorting long subject, [@ uprv_uca_getRawFromImplicit], [@ tiny_malloc_from_free_list | szone_malloc], [@ szone_free | free | ucol_setVariableTop], [@ libicucore.A.dylib@0xc43aa]

Martin, does that bug describe your issue?
(In reply to comment #3)
> very likely Bug 593132 - Mac crash sorting on subject or on startup [@
> UCGetCollationKey] sorting long subject, [@ uprv_uca_getRawFromImplicit], [@
> tiny_malloc_from_free_list | szone_malloc], [@ szone_free | free |
> ucol_setVariableTop], [@ libicucore.A.dylib@0xc43aa]
> 
> Martin, does that bug describe your issue?

=> incomplete without a reply from Martin
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.