Closed Bug 76167 Opened 24 years ago Closed 24 years ago

crash in image insert dialogue (Classic skin)

Categories

(Core :: DOM: Editor, defect)

PowerPC
Mac System 9.x
defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 76407

People

(Reporter: tracy, Assigned: pavlov)

Details

(Keywords: crash)

Attachments

(1 file)

seen on mac commercial build 2001-04-16-trunk -open composer window -click on Image insert (dialogue opens) -select an image to insert -type in alt text click Okay.... .....crash mac stdlog to follow
Keywords: crash
What format is the image you tried to insert? (gif, png, jpeg) Is the file local or remote (what url)?
Severity: critical → blocker
Keywords: smoketest
the image was a jpg stored locally.
I can't reproduce this on my Mac using today's build.
I'd have to guess this might be related to pavlov's fix for bug 75185.
This should go to pavlov if it's crashing in imageRequest code.
Assignee: beppe → pavlov
Ok, I'm a bonehead, I misread the Mac stacktrace. It's crashing in StyleSetImpl::CantRenderReplacedElement(), so I'll put this back on the editor plate until my build finishes and I can verify that the cause lies elsewhere.
Assignee: pavlov → beppe
This works fine for me on win32 as well, trunkbuild from 10 minutes ago.
Tracy, this is working for me on Win32, and I'm in sync with todays tip. Do you mind attatching the jpg that you are crashing with?
THis was reported as a Mac issue.
this worked fine on windows for me as well. bug is Mac only.
I am using the 4am bits from today on Mac. I have tried inserting jpegs from my local drive and I can't reproduce this problem. Tracy--is it just the one image or can you not insert any images? Can you load the images in the browser? Can you insert the images via drag & drop?
I am able to drag and drop the image. this is a work around, so reducing severity. it doesn't matter what image i use through the image insert dialogue...it always crashes. I believe this may be bug 76177.
Severity: blocker → critical
Keywords: smoketest
It was because of the CantRenderReplacedElement stack that I thought it might be related to pavlov's changes for bug 75185, although it's hard to tell exactly what the problem is without knowing which variable was null/garbage.
If it's really just Mac, it sure sounds like an imagelib issue to me.
linux commericial build 2001-04-16-10-trunk is okay..though it doesn't show the image in the preview pane... bug 71677
Target Milestone: --- → mozilla0.9.1
Sujay and I can't reproduce this on a Mac. Tracy--can you reproduce on any other Macintosh computers or just one? Maybe it's a problem with the cache or something like that? I think it should be resolved as worksforme.
okay we see the problem now. it happens on classic skin only. definitely a live problem. composer crashes immediately after choosing the image from image dialog. seen on 9.0 and 8.5 OS on Mac. Cc: Patty Mac qa_contact for Skins
I see the crash with the classic skin (not with Modern). I'm crashing in StyleSetImpl::CantRenderReplacedElement or near nsCSSFrameConstructor::CantRenderReplacedElement.
Summary: crash in image insert dialogue → crash in image insert dialogue (Classic skin)
I'm going to hand this over to pavlov ... sfraser spent some time debugging it, and we both feel this is an image problem, not something in the editor. I see several assertions being thrown before we crash as the result of nsImageFrame::OnStopDecode() calling presShell->CantRenderReplacedElement(): ###!!! ASSERTION: New URI failed: 'Error', file nsProtocolProxyService.cpp, line 302 ###!!! ASSERTION: frame already has posted event: '!*FindPostedEventFor(aFrame)', file nsFrameManager.cpp, line 1051 ###!!! ASSERTION: frame already has posted event: '!*FindPostedEventFor(aFrame)', file nsFrameManager.cpp, line 1051 ###!!! ASSERTION: frame already has posted event: '!*FindPostedEventFor(aFrame)', file nsFrameManager.cpp, line 1051
Assignee: beppe → pavlov
Target Milestone: mozilla0.9.1 → ---
this was not present on todays mac commercial build 2001-04-25-09-trunk
dup of 76407 which is fixed. *** This bug has been marked as a duplicate of 76407 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
verified in 4/25 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: