Sending mail using Microsoft Outlook Web Access crashes Mozilla

RESOLVED EXPIRED

Status

SeaMonkey
General
--
critical
RESOLVED EXPIRED
15 years ago
12 years ago

People

(Reporter: Chris Sokol, Assigned: asa)

Tracking

({crash})

Trunk
x86
Linux
crash

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 Galeon/1.2.9 (X11; Linux i686; U;) Gecko/20030314
Build Identifier: Mozilla/5.0 Galeon/1.2.9 (X11; Linux i686; U;) Gecko/20030314

Crash (a segfault) occurs 85% of the time.  Happens in both Mozilla and Galeon,
and in Mozilla on Windows as well.  No attachments are necessary.  Nothing else
within MSOWA causes a crash.  The mail is sent properly before crashing.

Reproducible: Always

Steps to Reproduce:
1.Log into Outlook Web Access.
2.Click the new email icon.
3.Write some stuff and click send.

Actual Results:  
The mail is sent, then Mozilla segfaults.

Expected Results:  
Sent the mail and not segfaulted!

Modern theme, no other changes to the default environment.

Comment 1

15 years ago
Does talkback trigger? If yes, please include talkback ID

Comment 2

14 years ago
I confirm this bug.

yes, quiet annoying. I still need to use now internet explorer and can't get rid
of windows.

The next problem also exists in the microsoft outlook web access server.
http://bugzilla.mozilla.org/show_bug.cgi?id=187883

And yes, that's a mistake of Microsoft, but it forces us working with IE and
windows.
Product: Browser → Seamonkey

Comment 3

13 years ago
Is this still a problem?  If so, please provide a talkback ID for the crash.
Severity: normal → critical
Keywords: crash
WFM Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050408
Mnenhy/0.7.2.0 and Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2)
Gecko/20050408 Firefox/1.0+

Tested with OWA from a Exchange 2003 SP1 & Windows 2003 Ent. Srv SP1
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.