Closed Bug 84795 Opened 23 years ago Closed 23 years ago

Copying a large number of addresses between address books causes crash

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect, P3)

Product:
SeaMonkey
Component:
MailNews: Address Book & Contacts
Platform:
All
Windows 2000
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
mozilla0.9.8

People

(Reporter: chuang, Assigned: sspitzer)

Details

(Keywords: crash, Whiteboard: nab-copy) 

This is opened for bug 82991.  We need to do the right fix for the crash.  I
think the problem is there is AddListener() call in
nsAbMDBRDFResource::GetAbDatabase() which is not the right thing to do.  Not all
the place calling GetAbDatabase() need to do AddListener().  

The fix should remove the hack fix in bug 82991 and do the righ fix.
Status: NEW → ASSIGNED
Severity: normal → critical
Keywords: crash
Keywords: nsenterprise
adding nsenterprise+
Keywords: nsenterprise → nsenterprise+
Priority: -- → P3
Target Milestone: --- → mozilla0.9.4
QA Contact: fenella → nbaca
Move to 0.9.5
Target Milestone: mozilla0.9.4 → mozilla0.9.5
This is ugly.  Should fix for next release.  marking nsenterprise-.
Keywords: nsenterprise+ → nsenterprise-
moving to 0.9.6
Target Milestone: mozilla0.9.5 → mozilla0.9.6
reassigning to cavin
Assignee: chuang → cavin
Status: ASSIGNED → NEW
moving to 1.0
Target Milestone: mozilla0.9.6 → mozilla1.0
moving out, but cc'ing Seth in csae this is something he's working on with any
listener changes he wrote.
Target Milestone: mozilla1.0 → mozilla1.2
Whiteboard: nab-copy
taking, I'm going to claim that the AB_OUTLINER_BRANCH landing fixed this.
Assignee: cavin → sspitzer
fixed.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Target Milestone: mozilla1.2 → mozilla0.9.8
Trunk build 2002-02-01-03: WinMe
Trunk build 2002-02-01-08: Linux RH 7.1
Trunk build 2002-02-01-08: Mac 10.1
Verified Fixed. Copied between 5,000-7,000 addresses and no crash.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.