Closed Bug 231821 Opened 22 years ago Closed 20 years ago

splash is listed in command line help, but it crashes mozilla

Categories

(Firefox :: General, defect, P2)

All
Linux
defect

Tracking

()

RESOLVED WORKSFORME
Firefox1.0beta

People

(Reporter: alpeterson, Assigned: mconnor)

Details

(Keywords: crash)

Attachments

(2 files)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7a) Gecko/20040120 Firebird/0.8.0+ Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7a) Gecko/20040120 Firebird/0.8.0+ Mozilla Firebird crashes when passed -splash or --splash not when passed -cow Please enable it or get rid of it... it is very confusing... this is not a dupliacte of other ones ... because this is marking a crash and or documentation error. bash-2.05b$ cd MozillaFirebird bash-2.05b$ ./MozillaFirebird --splash /home/aaron/work/firebird/MozillaFirebird/run-mozilla.sh: line 451: 2245 Segmentation fault (core dumped) "$prog" ${1+"$@"} bash-2.05b$ ./MozillaFirebird --help Usage: ./MozillaFirebird-bin [ options ... ] [URL] where options include: X11 options --display=DISPLAY X display to use --sync Make X calls synchronous --no-xshm Don't use X shared memory extension --xim-preedit=STYLE --xim-status=STYLE --g-fatal-warnings Make all warnings fatal Mozilla options -height <value> Set height of startup window to <value>. -h or -help Print this message. -installer Start with 4.x migration window. -width <value> Set width of startup window to <value>. -v or -version Print ./MozillaFirebird-bin version. -CreateProfile <profile> Create <profile>. -P <profile> Start with <profile>. -ProfileWizard Start with profile wizard. -ProfileManager Start with profile manager. -SelectProfile Start with profile selection dialog. -UILocale <locale> Start with <locale> resources as UI Locale. -contentLocale <locale> Start with <locale> resources as content Locale. -remote <command> Execute <command> in an already running Mozilla process. For more info, see: http://www.mozilla.org/unix/remote.html -splash Enable splash screen. -jsconsole Start with Javascript Console -edit <url> Start with editor. -chrome <url> Load the specified chrome. -inspector <url> Start with the DOM Inspector. bash-2.05b$ ./MozillaFirebird -splash /home/aaron/work/firebird/MozillaFirebird/run-mozilla.sh: line 451: 2549 Segmentation fault (core dumped) "$prog" ${1+"$@"} bash-2.05b$ ./MozillaFirebird -cow bash-2.05b$ Reproducible: Always Steps to Reproduce: 1. ./MozillaFirebird --splash 2. hehe... splash and crash rhyme! 3. and the ./MozillaFirebird --help to see it listed there. Actual Results: hehe... it... hehe It's core splashed! Expected Results: shown a splash screen or not shown splash in help and !!! not crash when passed unhandeled options. I think I remember this happening on windows too. critical because it crashes... I don't see how it could loose data... but it is very bad none the less
Not going to enable it. You know that already if you read your bugmail. However, it shouldn't crash.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: crash
Hardware: PC → All
Backtrace of the -splash & crash. Simply use firefox -splash Wheres the bug mail that mentioned Mike Connor? That way I wouldn't be adding to the confusion :)
Attachment #141491 - Flags: review?(firefox)
Flags: blocking0.9?
Comment on attachment 141491 [details] [diff] [review] Hack to disable -splash and remove from list of command line options moving over to someone who's more likely to know this part of the code better. Brian, this has the net effect of making it impossible to utilize the -splash parameter with any MOZ_XUL_APP app. Is this desired?
Attachment #141491 - Flags: review?(firefox) → review?(bryner)
QA Contact: mconnor
Comment on attachment 141491 [details] [diff] [review] Hack to disable -splash and remove from list of command line options There's a better way to fix this. nsXULAppAPI has a field for whether the app has a splash screen. I had been using it for the default state of the splash screen, but I'm thinking if it's set to false we should not allow the splash screen to be enabled at all.
Attachment #141491 - Flags: review?(bryner) → review-
taking
Assignee: firefox → mconnor
Priority: -- → P2
Target Milestone: --- → Firefox0.9
pushing to 1.0beta, since this is of limited visibility. minusing blocking0.9? for the same reason
Flags: blocking0.9? → blocking0.9-
Target Milestone: Firefox0.9 → Firefox1.0beta
worksforme with firefox 0.10.1
Seems to be WFM, please reopen if this can be reproduced on trunk nightlies.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: