246612 - Segmentation fault when firing alarms that send mail notification

Status: RESOLVED FIXED

(Calendar :: General, defect)

Description

[Federico Tello Gentile]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

I ran into a segmentation fault upon starting calendar (version 2004040815-cal).
It happens when I have more than 1 alarm that is set to send an email and I'm
not connected to the net (dial up) and since I don't have the SMTP password in
the password manager it fails to send the alarm notification so a window appears
telling me that right before the alarm notifications (2 or more in a single
dialog  window). When the last alarm window opens the whole application crashes.

Reproducible: Always
Steps to Reproduce:
1) Delete the stored password in the SMTP server setting in passeord manager
2) Make sure the browser is not setted for offline browsing.
3) Run Calendar inside Mozilla, create 2 events in the past and set them to fire
an alarm and send an email.
4) Make sure you are not connected to The Internet
5) Whenever the alarms fire, a message appears telling it cold not conect to the
SMTP and a segmentation fault follows.
Actual Results:  
Segmentation fault.

Expected Results:  
Not crashing.

Closing the warning message before the alarm windows appear prevents the
segmentaion fault.
In my view there must be some unexpected situation between this warning dialog
(that tells me the SMTP was not found) and the alarm windows.

I run Fedora core 2 official build.

Comment 1

[Justin Wood (:Callek)]

Hmm does this happen if you only do ONE alarm, not two?

Also can you download Mozilla 1.7rc3 and try this, if not fixed try again with a
clean profile?

-->Crash keyword, based on Description, if I mis-interpreted `segfault` and it
is not a crash, please comment that and I'll remove the keyword

Comment 2

[Federico Tello Gentile]

Yes, it is a crash. I am now on my windows PC and using 1.7rc3, installed this
http://ftp.mozilla.org/pub/mozilla.org/calendar/xpi/windows/calendar_windows_nightly.xpi
version that is listed on the calendar webpage. I created a fresh profile and
created an event with an alarm attached and a mail notification. If I create the
event in a point in time that makes the alarm fire immedately it crashes. If I
create it in the future so the alarm does not fire, it does not crrash.
I cannot reproduce the same steps here because calendar crashes faster and more
often. I'll try test creating only 1 alarm, but I think I didn't see the crash
when I had only 1 event scheduled.
I have been sending crash data to the talkback agent all morning. Maybe you can
check that out. The first crash report had my email (the one I use here in
bugzilla) and a short description that mentioned Calendar.

Comment 3

[gekacheka]

Mostafah has provided a *test* xpi of 20040609 that fixed some alarm crashes
(bug 245981, bug 245585), so you might try that.
ftp://ftp.mozilla.org/pub/mozilla.org/calendar/xpi/

To provide the talkback ids, see
http://bugzilla.mozilla.org/show_bug.cgi?id=245981#c3 

Comment 4

[Federico Tello Gentile]

The test build seems to solve the crashed on windows. Too bad I can't use the
linux version it on my mozilla 1.6 (or can I?).
Just in case, the crash is here Incident ID: 93165 but it seems the same problem
described in bug 245981.

I'll do a little more testing on linux, but I look forward to get 1.7 final and
install a newer calendar xpi.

Comment 5

[Justin Wood (:Callek)]

hmm, try 1.7rc3 on linux? with the latest cal version for linux?

If it works there, I'll resolve fixed

Comment 6

[Martin Bagge / brother]

reporter, have you tried later versions of moz/tb and calendar?

Comment 7

[Federico Tello Gentile]

I tried mozilla Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a4) Gecko/20040927
using calendar 2004091012 and it does not crash. I will test this on linux when
1.8 official is released since I don't use mozilla's alphas or betas on linux
(too much dial up time downloading 2 versions every time and I don't want to
risk the profile I use for the real improtant stuff).

So close this bug and I'll file a new one if I ever see the issue again.

Comment 8

[Justin Wood (:Callek)]

If the issue is still around on your linux box, please just comment here asking
for it to be re-opened. No need for a new bug which _is_ a duplicate of this.

Comment 9

[Reed Loden [:reed]]

The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!