hangs when I try to compose a new mail and I click into insert -> image and I select a jpeg larger than 300kb with more Height than Weight

RESOLVED EXPIRED

Status

--
critical
RESOLVED EXPIRED
16 years ago
10 years ago

People

(Reporter: JMELEN, Assigned: bugzilla)

Tracking

({hang})

Trunk
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/00200302
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/00200302

I'm using SuSE 8.1 and I have one of the latest builds of mozilla, but I tested
this with stable version too. If you click on mozilla-mail, and you compose a
new mail, click on insert -> image and select a jpeg larger than 300kb with more
height than weight. My system hangs (I need to press the reset button).

Reproducible: Always

Steps to Reproduce:
1.Open Mozilla mail and click on compose new mail
2.click into insert -> Image
3.Select a JPEG larger than 300kb with more height than weight


Actual Results:  
My system hangs (stop responding)


I think that is a fault of the preview feature of mozilla mail

Comment 1

16 years ago
Reporter, what is the build ID you are using? (The numbers at the top of the
titlebar.)

Please try this. Close Mozilla. Go to your profile directory and delete the
xul.mfasl file. Restart Mozilla. Does that solve the problem?
Keywords: hang
Summary: crash (my system hangs) when I try to compose a new mail and I click into insert -> image and I select a jpeg larger than 300kb with more Height than Weight → hangs when I try to compose a new mail and I click into insert -> image and I select a jpeg larger than 300kb with more Height than Weight

Comment 2

16 years ago
Hi, we're using Mozilla 1.3b - Build ID: 20030209. Yesterday's CVS for SuSE 8.1

I deleted XUL.mfasl and I restarted mozilla mail, but the problem is still there...
(Reporter)

Comment 3

16 years ago
Mozilla {Build ID:20030209}. I'm using this CVS version:

ftp.suse.com:/pub/projects/mozilla/experimental/1.3b

-rw-r--r--    1 suse     susewww    268611 Jan 17 06:36 libical-20030116-0.i386.rpm
-rw-r--r--    1 suse     susewww    519192 Jan 17 06:36 libical-20030116-0.src.rpm
-rw-r--r--    1 suse     susewww    147649 Jan 17 06:36
libical-devel-20030116-0.i386.rpm
-rw-r--r--    1 suse     susewww  11040301 Feb 10 08:14 mozilla-1.3b-0.i386.rpm
-rw-r--r--    1 suse     susewww  32454007 Feb 10 08:14 mozilla-1.3b-0.src.rpm
-rw-r--r--    1 suse     susewww   2954083 Feb 10 08:14
mozilla-devel-1.3b-0.i386.rpm
-rw-r--r--    1 suse     susewww    253308 Feb 10 08:14
mozilla-dom-inspector-1.3b-0.i386.rpm
-rw-r--r--    1 suse     susewww    166351 Feb 10 08:15 mozilla-irc-1.3b-0.i386.rpm
-rw-r--r--    1 suse     susewww   1912512 Feb 10 08:15 mozilla-mail-1.3b-0.i386.rpm
-rw-r--r--    1 suse     susewww    258666 Feb 10 08:15
mozilla-venkman-1.3b-0.i386.rpm
-rw-r--r--    1 suse     susewww    133234 Feb 10 08:15
mozilla-xmlterm-1.3b-0.i386.rpm

Updated

16 years ago
Blocks: 193931

Comment 4

16 years ago
-- Is the computer you are running Mozilla on running an antivirus program? If
so, please detail what program and what version it is. Temporarily disable the
antivirus program. Then try to reproduce the problem you describe. Does the
problem still occur?

-- Go to Edit | Mail & Newsgroup Account Settings | Outgoing Server (SMTP) and
check "never" on whether to use a secure connection (SSL). Now try to reproduce
the problem. Does it still occur?

-- Go to Edit | Mail & Newsgroup Account Settings. In the appropriate account,
under Copies & Folders, unselect "place a copy in." Now try to reproduce the
problem. Does it still occur? If this works, is this an IMAP account? Are there
many messages in the sent folder?

-- Is the computer behind a firewall? If so, temporarily disable it, or put the
computer directly on the Internet. Can you still reproduce the problem? If not,
what product and version number is the firewall?

-- Delete all your SMTP server entries. Exit Mozilla. Restart Mozilla. Recreate
all your SMTP server entries. Can you still reproduce the problem?

-- Do you have spellchecker installed? If so, disable it or remove it. Does that
solve the problem?

-- Is your profile hosted on a network drive (or NFS mount)? 

If none of these steps work, please attach an SMTP log. The steps for creating
the log can be found here:

http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap
(Reporter)

Comment 5

16 years ago
have you read all the Additional Comments???, if so, please, read it again.

Comment 6

16 years ago
Right. Sorry. Is this a duplicate of bug 151097?
No longer blocks: 193931
(Reporter)

Comment 7

16 years ago
No, it is not.
Product: MailNews → Core
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: 13 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.