Closed Bug 10291 Opened 25 years ago Closed 25 years ago

Dismissing ABook Card that was opened in Address picker after Address pickeris closed leads to a crash

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

x86
Windows NT

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 10349

People

(Reporter: marina, Assigned: hangas)

Details

Steps to reproduce:
-bring up Address Book;
-create a new card with no email address in it;
-OK the dialog box and see the card is now in the right thread pane under ABook;
-go to the Messenger;
-open New Mail Composition window;
-click on the Address icon which will bring you AB;
-select a card with no e-mail address;
-click this card, click "To", OK dlg box;
(note the addressee is entered in the New mail Composition window dispite the
missing e-mail address)
-now try to dismiss the card by clicking either OK or Cancel
= this causes crash
(might be designed not to let the window go without e-mail address but should
not crash)
QA Contact: lchiang → esther
Marina, pls specify the build you used.
My bad, this bug was observed with 1999-07-21-11-M9/ windows build on US NT40
Assignee: phil → hangas
reassigning to hangas
Marina, in your steps (step 8)  are you trying to dismiss the card or the compose window.  If the card, did you  bring the Address Book back and select the card then Delete it.    If you are dismissing the card after opening the Address Book again, there is a bug 10290 about deleting a card crashing and this would be a duplicate of that bug.
 If it's dismissing the Compose window after realizing the address is incomplete I can't reproduce that.
I'm trying to dismiss the card after i closed the address picker dialog box by
clicking OK. When Address picker is gone the card is still on the screen and i
want to close it by clicking OK. As soon as i'm attempting to do so it crashes
(reproduced it in today's 1999-07-22-08-M9 Windows build)
Marina, when I click OK after creating a New Card the card is not still opened.
Therefore, when I call the Address Picker, then close it the card is not opened.
We are getting different results, I will come to your cube to see how you are
doing this so I can try to reproduce it.
Summary: Dismissing ABook Card that has no email address in it after using it through Address picker leads to a crash → Dismissing ABook Card that was opened in Address picker after Address pickeris closed leads to a crash
OK, after watching Marina there is one step missing and the bug summary will
change.  When the address picker comes up, she double-clicks on the card, which
opens the card.  Then she clicks on the To: button to put the card in the
Addressing pane.   This means the Address Picker is opened at the same time a
card is opened, when she trys to close the card with the OK button, it crashes.
After trying several things I found any card will cause the crash (not one
missing the email address) and you don't have click the To: button in the picker
to make this happen.
The scenario is:
1. Launch Messenger
2. Click New Msg (have at least 1 card in your personal Address Book)
3. Click Address (to bring up the picker)
4. Select Personal Address book to display the cards
5. Double click on a card (it will open the card, note: in 4.5x it puts the card
in the bucket)
6. Close the Address picker
7. Ok the card.
Crash
Not sure if the bug is:
1. When you open a card while in the address picker (by double clicking), then
close the address picker, then try to close the card you will crash.
2. Double-clicking on a Card in the Address picker should not open the card, but
put the name in the bucket defaulting with To:
I will check the spec to see if it's documented, in any case we shouldn't crash.
Talkback incident 11472837


 Call Stack:    (Signature = XPC3250.DLL + 0x75e5 (0x605f75e5) 74a3c9d0)
 XPC3250.DLL + 0x75e5 (0x605f75e5)
 XPC3250.DLL + 0x81ec (0x605f81ec)
 JS3250.DLL + 0x17101 (0x606d7101)
 JS3250.DLL + 0x13518 (0x606d3518)
 JS3250.DLL + 0x172c2 (0x606d72c2)
 JS3250.DLL + 0x13518 (0x606d3518)
 JS3250.DLL + 0x172c2 (0x606d72c2)
 JS3250.DLL + 0x13518 (0x606d3518)
 JS3250.DLL + 0x172c2 (0x606d72c2)
 JS3250.DLL + 0x13518 (0x606d3518)
 JS3250.DLL + 0x13649 (0x606d3649)
 JS3250.DLL + 0x39e4 (0x606c39e4)
 JSDOM.DLL + 0x16635 (0x60716635)
 RAPTORHTML.DLL + 0x8ced4 (0x6032ced4)
 RDF.DLL + 0x1e2f9 (0x603ce2f9)
 RAPTORHTML.DLL + 0x8deee (0x6032deee)
 RAPTORHTML.DLL + 0x8d791 (0x6032d791)
 RAPTORHTML.DLL + 0x25068 (0x602c5068)
 RAPTORVIEW.DLL + 0x1d4e (0x60941d4e)
 RAPTORVIEW.DLL + 0x63cf (0x609463cf)
 RAPTORVIEW.DLL + 0x2416 (0x60942416)
 RAPTORWIDGET.DLL + 0x4fae (0x60964fae)
 RAPTORWIDGET.DLL + 0x4ff4 (0x60964ff4)
 RAPTORWIDGET.DLL + 0x75f9 (0x609675f9)
 RAPTORWIDGET.DLL + 0x7859 (0x60967859)
 RAPTORWIDGET.DLL + 0x6e96 (0x60966e96)
 RAPTORWIDGET.DLL + 0x50c3 (0x609650c3)
 KERNEL32.DLL + 0x3663 (0xbff73663)
 KERNEL32.DLL + 0x228e0 (0xbff928e0)
 0x00638c1c

 Registers:
 EAX:
 00000000
 EBX:
 00000000
 ECX:
 00000000
 EDX:
 0000002f
 ESI:
 01e57970
 EDI:
 01e57890
ESP:
0063ef68
EBP:
0063ef7c
EIP:
605f75e5
cf PF af ZF sf of IF df nt RF vm   IOPL: 0
CS:
0137
DS:
013f
SS:
013f
ES:
013f
FS:
5b17
GS:
0000
Status: NEW → ASSIGNED
Target Milestone: M9
In today's build 1999-07-30 you can not enter ABook Card, when you click OK it
is either doesn't have any effect or crashes.
Build 1999073011M9/Necko: Win32/NT4

The first time I selected a New Card and entered some text, an email and some
phone numbers and pressed OK nothing happened. The second time it crashed but I
have not been able to duplicate the crash. If it happens again I'll get a stack
trace. Esther also saw similar results on her Linux system with today's build.
Sorry, please disregard my previous entry. It's doesn't specifically apply to
this bug.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
This is the same problem as 10349.  If the New Card dialog had been modal then
this could not happen.  Marking as dup.


*** This bug has been marked as a duplicate of 10349 ***
Status: RESOLVED → VERIFIED
verified dup
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.