Closed Bug 235673 Opened 20 years ago Closed 19 years ago

crash running xulmaker 0.5

Categories

(Core :: XUL, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: pashute, Assigned: hyatt)

Details

(Keywords: crash, qawanted)

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040219

Install seems problematic - see steps to reproduce.
Still, install steps said OK, and new tool shows in menu, 
but running it, crashes the mozilla.

Reproducible: Always
Steps to Reproduce:
1. Installing XulMaker 0.5
  a. First wants jslib. 
     Installed that, says install ok, and when leave mozilla: crash
  b. Install XulMaker 0.5 
     Installed OK, when close mozilla: crash.
2. Run XulMaker from menu (Tools/Web Development)
     ** CRASH **
Actual Results:  
Crash

Expected Results:  
At least stay alive, 
and of course should bring up the XUL-Maker.


Before installing the Alpha, I removed the old Mozilla using Add/Remove programs.
It said that not everything was removed....
Where is this XulMaker thing gotten from?
(In reply to comment #1)
> Where is this XulMaker thing gotten from?

http://xulmaker.mozdev.org/
Ah, ok.  Sicking, chances are this is yours....
Can you try this with a recent nightly. A crashfix went in on february 24th so
please try a build from 25th or later.
(In reply to comment #4)
> Can you try this with a recent nightly. A crashfix went in on february 24th so
> please try a build from 25th or later.

Confirm with "Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7b) Gecko/20040315".

No crash after jslib install.
Jslib install verification (chrome://jslib/content) works as described at
jslib.mozdev.org (it shows the jslib splash screen).

No crash after xulmaker install.

Still the same behaviour with invoking xulmaker from menu, mozila simply dies.

Steps to reproduce the same as in original bug report.
The sources of jslib and xulmaker are the same (jslib.mozdev.org,
xulmaker.mozdev.org).

bb4now,
PMC
Keywords: qawanted
(In reply to comment #5)

OK, this is a regression thing. I tried current nightly plus all official
releasses down to 1.4.1:

Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7b) Gecko/20040315
jslib install: OK
xulmaker install: OK
xulmaker invocation: Mozilla crashes with "Meet Dr. Watson" thingie :(

Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.6) Gecko/20040113
jslib install: OK
xulmaker install: OK
xulmaker invocation: Mozilla crashes with "Meet Dr. Watson" + Talkback

Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.5) Gecko/20031007
jslib install: OK
xulmaker install: OK
xulmaker invocation: Mozilla crashes with "Meet Dr. Watson" + Talkback

Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4.1) Gecko/20031008
jslib install: OK
xulmaker install: OK
xulmaker invocation: Success

Hope this helps, I am going to try to confirm this later from Linux environment.

bb4now,
PMC
OK, I have confirmation for this bug on WinNT 4.0 and Linux versions from
yesterdays nightly down to (and including) 1.5.

The reduced test case looks like this:

/// xulcrash.xul ///
<?xml version="1.0"?>
<window	xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">
	<toolbar>
		<arrowscrollbox>
			<menulist editable="true">
			</menulist>
		</arrowscrollbox>
	</toolbar>
</window>
/// END ///

Just load the above code and mozilla will crash.

Please someone escalate this back to confirmed.

bb4now,
PMC
this can't be mine since none of my attributes code went into 1.5. Marking
confirmed though since Marin has obviously tested this.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Didn't someone mention that trees don't like being in scrollable views either?
Severity: normal → critical
Keywords: crash
Marin's testcase from comment 7 worksforme with linux trunk 2005061808.
Is anyone still seeing this in a recent build?
Works for me on trunk too.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: shrir → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.