Closed Bug 80025 Opened 24 years ago Closed 24 years ago

Composer crash when opening document with CSS

Categories

(Core :: DOM: Editor, defect, P1)

x86
Linux
defect

Tracking

()

VERIFIED INVALID
mozilla0.9.1

People

(Reporter: spam, Assigned: kinmoz)

Details

(Keywords: crash)

Attachments

(1 file)

RH7.1, 7 hours old optimized CVS build: crash when opening document in composer To repro: start mozilla open composer select File/Recent Pages and then select a file there Crash. Tested this several times - same crash.
Attached file backtrace (non-debug)
Severity: normal → critical
Cc: shrir.
tested some more: This only seems to happen when the document contains CSS They used to load fine untill recently. A sample of a page that crashes is found at http://home.c2i.net/dark/documents.html
Summary: Composer crash when opening document → Composer crash when opening document with CSS
I just tried this with random non-CSS pages in my recent file menu list...no crash. works fine.. then I tried with your page with CSS...still no crash...I can load that page from my Recent File menu..
but wait, I 'm using yeterdays build....lemme try todays...
I just tried this with random non-CSS pages in my recent file menu list...no crash. works fine.. then I tried with your page with CSS...still no crash...I can load that page from my Recent File menu..
No crash with yesterday's linux build on http://home.c2i.net/dark/documents.html Very nice page design btw, clear and readable.
thanks - it's one in a series of good intentions - WIP. The build that crashes origins from a pull at around 22:55 bonsai time yesterday (after the bidi checkins). Clobbered before build. .mozconfig: ac_add_options --disable-debug ac_add_options --disable-tests ac_add_options --enable-optimize=-O2 ac_add_options --disable-logging ac_add_options --enable-crypto RH7.1 gcc-2.96-81. I'll do some tests with the optimize flags over the next builds - see what happens.
I'll also try this out in a current build...today's 5/10 build crashes for me...
tried on today's 5/10 build...works fine...
Hmm. I loaded it in browser and tried to open it with "open web location" to see if that changed anything, but nothing ever opened. Odd. I'll repull and build with -O1 now.
This may not be related to CSS at all, allthough it makes it easyer to trigger: I now got the same crash once by merely opening composer. And on one occation the document loaded in composer after i first had clicked in the composer page (i noticed toolbar icons shifted some at that point), but a second after having closed composer the same crash occured. Rebuilding with -O2 first without clobbering. This is so guaranteed "crashy" here perhaps i missed something :/
assigning to kin for review and initial debug
Assignee: beppe → kin
Keywords: crash
Priority: -- → P1
Target Milestone: --- → mozilla0.9.1
Since the crash seems to involve "SetDataWithLength": I notice some warnings during build - of many alike are these: In file included from nsPrefService.cpp:28: nsPrefBranch.h:74:3: warning: pasting "->" and "GetData" does not give a valid preprocessing token nsPrefBranch.h:74:3: warning: pasting "->" and "SetData" does not give a valid preprocessing token nsPrefBranch.h:74:3: warning: pasting "->" and "ToString" does not give a valid preprocessing token nsPrefBranch.h:74:3: warning: pasting "->" and "SetDataWithLength" does not give a valid preprocessing token nsPrefBranch.h:74:3: warning: pasting "->" and "AdoptData" does not give a valid preprocessing token nsPrefBranch.h:74:3: warning: pasting "->" and "AdoptDataWithLength" does not give a valid preprocessing token nsPrefBranch.h:75:3: warning: pasting "->" and "GetType" does not give a valid preprocessing token
that last comment may not be significant at all. I compared some of the warnings i get with the ones tinderbox reports - i probably get several thousand more warnings than are listed there, whereof a thousand are those "does not give a valid preprocessing token".
no luck with this rebuild - the crash is with me.
The crash is real enough but my compiler is not the official Mozilla one. Hyatt just wrote in n.p.m.builds that users are to downgrade to egcs again. Since others don't see this bug, it's obviously a problem only with my own compiler - thus resolving as invalid.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
four letter words...five letter words.. that was LEAF writing in the newsgroup, not at all Hyatt.
verified.
Status: RESOLVED → VERIFIED
turns out this is bug 80097. I crash there all the time, with the latest nightly also when starting browser or adding comment in bugzilla.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: