Closed Bug 281212 Opened 20 years ago Closed 18 years ago

Crash in html email composer with Format > Image Properties [@ nsNntpCacheStreamListener::OnStartRequest ]

Categories

(MailNews Core :: Networking: NNTP, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: rinaldij, Assigned: sspitzer)

Details

(Keywords: crash)

Crash Data

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

When replying to an html message that contains an image (shift reply from text
mode) an y attempt to alter the image properties via Format > Image Properties
the suite segfaults.

Reproducible: Always

Steps to Reproduce:
1.Select a news message containing an image
2.Reply in html mode.  This loads the image in the Reply composer
3.Attempt to reformat the image by selecting the image and clicking Format >
Image Properties.

Actual Results:  
Entire suite closes

Expected Results:  
Allow resize or whatever operation one wants to perform on the image.

This has also happened in Mac OS and Windows reported to me by different users.

A linux gdb bt shows:

gdb) bt
#0  0x40967f76 in nanosleep () from /lib/libc.so.6
#1  0x00000000 in ?? ()
#2  0x40967dbf in sleep () from /lib/libc.so.6
#3  0x08057f81 in ah_crap_handler (signum=11) at nsSigHandlers.cpp:132
#4  0x41ace2a6 in nsProfileLock::FatalSignalHandler (signo=11) at
nsProfileLock.cpp:209
#5  0x4027cc85 in __pthread_sighandler () from /lib/libpthread.so.0
#6  <signal handler called>
#7  0x42656f4a in nsNntpCacheStreamListener::OnStartRequest (this=0x93b5180, 
request=0x925f2f8, aCtxt=0x0) at nsNNTPProtocol.cpp:658
#8  0x40dcc9c3 in nsInputStreamPump::OnStateStart (this=0x925f2f8) at
nsInputStreamPump.cpp:381
#9  0x40dcc8da in nsInputStreamPump::OnInputStreamReady (this=0x925f2f8, 
stream=0x8e238c4) at nsInputStreamPump.cpp:337
#10 0x400ddc19 in nsInputStreamReadyEvent::EventHandler (plevent=0x0)
at nsStreamUtils.cpp:118
---Type <return> to continue, or q <return> to quit---
Assignee: guifeatures → sspitzer
Component: XP Apps: GUI Features → Networking: News
Keywords: crash
Product: Mozilla Application Suite → Core
Version: unspecified → Trunk
This appear to work for me using Thunderbird 1.0 on WinXP, is it a regression ?
Do you work in off-line mode, does it crash immediately after clicking image
properties (or double-clicking the image) ?
OS: Linux → All
Hardware: PC → All
Summary: Crash in html email composer with Format > Image Properties → Crash in html email composer with Format > Image Properties [@ nsNntpCacheStreamListener::OnStartRequest ]
(In reply to comment #1)
> This appear to work for me using Thunderbird 1.0 on WinXP, is it a regression ?
> Do you work in off-line mode, does it crash immediately after clicking image
> properties (or double-clicking the image) ?

Not working in off line mode. The crash occurs (freeze in debug mode) as soon as
the Properties box is rendered.  It's not up long enough to read the widgets.
When I tested it. I was online. 

Mac OSX.3.7 Mozilla 1.8.a.5

wasn't willing to try offline.

when Mozilla's Bug reporter came up I filled out the crash report.

Also It caused Mac OSX's Crash Reporter to come up as well. I filled that out
and sent in. as well.

So its bad enough on Mac OSX to cause system crash/error reporter to come up.
I had to double-click the image to crash Mozilla, if i go the Format > Image
Properties way, it doesn't crash.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Please change status to resolved.  

I don't get enough html mail to know exactly when the problem ceased, but recent CVS builds do not have the problem.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
No specific bug / patch referenced as the fix.

-> WORKSFORME
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 18 years ago18 years ago
Resolution: --- → WORKSFORME
Product: Core → MailNews Core
Crash Signature: [@ nsNntpCacheStreamListener::OnStartRequest ]
You need to log in before you can comment on or make changes to this bug.