88741 - crash using mozilla -remote openFile (localfile)

Status: RESOLVED WORKSFORME

(Core Graveyard :: X-remote, defect)

Description

[Len Trigg]

When mozilla is started using -mail option, access from -remote causes crashes.
To reproduce:

1) Start mozilla -mail
2) In another shell do a mozilla -remote call. I've found that a javadoc index
seems to do the trick repeatably, eg:
mozilla -remote 'openFile(/home/len/java_ext/src/doc/index.html)'

Actual result:
3) Mozilla crashes.
Expected result:
3) Mozilla opens a navigator window displaying supplied file.

Notes: 
Doing step 1 without the -mail option stops the crash.
Opening an empty nav window as step 1a does not stop the crash.
Opening a non-empty nav window as step 1a does not stop the crash.

I'm using Linux build 2001070210

Comment 1

[timeless]

please get a stacktrace or talkback report

Comment 2

[Len Trigg]

When I try this with "talkback enabled tar.gz" 0.9.2 milestone, the crashing of
the original mozilla (i.e. the -mail one, not the -remote one) gives this message:

Gdk-ERROR **: BadValue (integer parameter out of range for operation)
  serial 14902 error_code 2 request_code 12 minor_code 0

Should talkback do more than this?

Comment 3

[Len Trigg]

I made a debug build and did the steps. No corefile is generated when the first
mozilla dies. The final bunch of messages that come out look like this:

WARNING: cell content 0x43ba5dd8 has large width 687194880 
WARNING: cell content 0x43ba5f30 has large width 171798632 
WARNING: cell content 0x43ba60b0 has large width 687194880 
WARNING: cell content 0x43ba6208 has large width 171798632 
WARNING: cell content 0x43ba6388 has large width 687194880 
nsBlockReflowContext: TableOuter(table)(11)@0x43ba17dc metrics=858993782,8040!
Block(body)(2)@0x43b89160: line=0x43ba97e8 xmost=858993782
Block(body)(2)@0x43b89160: Init: bad caller: width WAS 858993808(0x33333490)
nsBlockReflowContext: Block(p)(13)@0x43ba66c0 metrics=858993808,240!
Block(body)(2)@0x43b89160: line=0x43ba9838 xmost=858993808
Block(body)(2)@0x43b89160: Init: bad caller: width WAS 858993808(0x33333490)
Block(body)(2)@0x43b89160: Init: bad caller: width WAS 858993808(0x33333490)
Block(body)(2)@0x43b89160: Init: bad caller: width WAS 858993808(0x33333490)
Block(td)(1)@0x43ba748c: Init: bad caller: width WAS 852403005(0x32cea33d)
WARNING: cell content 0x43ba748c has large width 852403005 
WARNING: cell content 0x43ba8c14 has large width 318552645 
WARNING: cell content 0x43ba8d5c has large width 533850330 
nsBlockReflowContext: TableOuter(table)(20)@0x43ba72f8 metrics=858993780,570!
Block(body)(2)@0x43b89160: line=0x43ba9888 xmost=858993780
Block(body)(2)@0x43b89160: Init: bad caller: width WAS 858993808(0x33333490)
Block(body)(2)@0x43b89160: Init: bad caller: width WAS 858993808(0x33333490)
nsBlockReflowContext: Block(body)(2)@0x43b89160 metrics=858993808,10695!
Area(html)(-1)@0x43b78e48: line=0x43b8e5a8 xmost=858993928
nsBlockReflowContext: Frame(frameset)(2)@0x43a97128 metrics=1073741952,1073741824!
Area(html)(-1)@0x43a96de4: line=0x43a97204 xmost=1073741952
Gdk-ERROR **: BadAlloc (insufficient resources for operation)
  serial 112819 error_code 11 request_code 53 minor_code 0
Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter)
  serial 112838 error_code 9 request_code 62 minor_code 0


There are actually smegloads of the WARNING, nsBlockReflowCount, and Block(body)
type messages.


Does this bug even happen for other people?

Comment 4

[Keyser Sose]

Marking NEW.

Comment 5

[Pete Collins (MDG)]

I can't duplicate on FreeBSD running off the trunk.

--pete

Comment 6

[Christopher Blizzard (:blizzard)]

This doesn't crash for me.  It has other issues, though.  I'll open another bug
for that.