If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

FF4b4 crashes on exotic Cmd+[non english alphabet] key combination

NEW
Assigned to

Status

()

Core
Widget: Cocoa
P3
critical
7 years ago
6 years ago

People

(Reporter: miceuz, Assigned: smichaud)

Tracking

({crash})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:2.0b4) Gecko/20100818 Firefox/4.0b4
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:2.0b4) Gecko/20100818 Firefox/4.0b4

i have installed a custom keyboard layout, which places the letter 'ž' on the
key 'w'. Firefox crashes every time i hit Cmd+ž to close the tab. This happens
when i press the Cmd+key combination for other national letters too.


Reproducible: Always

Steps to Reproduce:
1.download http://megalogika.stp.lt/mic/Lithuanian-ISOIEC9995.keylayout
2.save it to your /Library/Keyboard layouts
3.add it to your keyboar layout switcher and switch to this keyboard
4.start firefox 3
5.hit Cmd+w

Actual Results:  
firefox crashes

Expected Results:  
tab should be closed

this bug was on 1.9.1 gecko branch and was fixed then but after firefox moved to new gecko branch - it reapeared. 

the old bug is https://bugzilla.mozilla.org/show_bug.cgi?id=442245
(Reporter)

Comment 1

7 years ago
Created attachment 472964 [details]
a problematic keyboard layout
(Reporter)

Updated

7 years ago
Priority: -- → P1
(Reporter)

Updated

7 years ago
See Also: → bug 442245
(Reporter)

Comment 2

7 years ago
i can still reproduce it on Firefox 4 beta 5 

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:2.0b5) Gecko/20100101 Firefox/4.0b5
(Reporter)

Comment 3

7 years ago
crash is not reported in about:crashes

i've tried to install clean and crash report history is empty

Updated

7 years ago
Component: General → Widget: Cocoa
Keywords: crash, stackwanted
Priority: P1 → P3
Product: Firefox → Core
QA Contact: general → cocoa
miceuz, does the problem still occur in Firefox 6?
(Reporter)

Comment 5

6 years ago
i don't have Firefox 6 right now, i'm on 7 beta channel and i can confirm that bug still exists - FF just crashes - sometimes loosing all session information, sometimes not.



  Application Basics

        Name
        Firefox

        Version
        7.0

        User Agent
        Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:7.0) Gecko/20100101 Firefox/7.0

        Profile Directory

          Show in Finder

        Enabled Plugins

          about:plugins

        Build Configuration

          about:buildconfig

  Extensions

        Name

        Version

        Enabled

        ID

        Abduction!
        3.0.10
        true
        {b0e1b4a6-2c6f-4e99-94f2-8e625d7ae255}

        Adblock Plus
        1.3.9
        true
        {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}

        Ctrl-Tab
        0.21.1
        true
        ctrl-tab@design-noir.de

        DOM Inspector
        2.0.10
        true
        inspector@mozilla.org

        Flashblock
        1.5.15.1
        true
        {3d7eb24f-2740-49df-8937-200b1cc08f8a}

        Greasemonkey
        0.9.8
        true
        {e4a8a97b-f2ed-450b-b12d-ee082ba24781}

        StumbleUpon
        3.94
        true
        {AE93811A-5C9A-4d34-8462-F7B864FC4696}

        Test Pilot
        1.1.3
        true
        testpilot@labs.mozilla.com

        Firebug
        1.7.3
        false
        firebug@software.joehewitt.com

        Web Developer
        1.1.9
        false
        {c45c406e-ab73-11d8-be73-000a95be3b12}

  Modified Preferences

      Name

      Value

        accessibility.typeaheadfind
        true

        accessibility.typeaheadfind.flashBar
        0

        browser.history_expire_days.mirror
        180

        browser.places.createdSmartBookmarks
        true

        browser.places.importBookmarksHTML
        false

        browser.places.importDefaults
        false

        browser.places.leftPaneFolderId
        -1

        browser.places.migratePostDataAnnotations
        false

        browser.places.smartBookmarksVersion
        2

        browser.places.updateRecentTagsUri
        false

        browser.startup.homepage_override.buildID
        20110824172139

        browser.startup.homepage_override.mstone
        rv:7.0

        browser.tabs.warnOnClose
        false

        extensions.lastAppVersion
        7.0

        general.useragent.extra.ubiquity

        network.cookie.cookieBehavior
        1

        network.cookie.prefsMigrated
        true

        places.database.lastMaintenance
        1314181053

        places.history.expiration.transient_current_max_pages
        64424

        places.last_vacuum
        1280128933

        print.macosx.pagesetup-2
        PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPCFET0NUWVBFIHBsaXN0IFBVQkxJQyAiLS8vQXBwbGUvL0RURCBQTElTVCAxLjAvL0VO…

        print.print_bgcolor
        false

        print.print_bgimages
        true

        print.print_command

        print.print_downloadfonts
        true

        print.print_evenpages
        true

        print.print_footerleft

        print.print_footerright

        print.print_headerleft

        print.print_headerright

        print.print_in_color
        true

        print.print_margin_bottom
        0.5

        print.print_margin_left
        0.5

        print.print_margin_right
        0.5

        print.print_margin_top
        0.5

        print.print_oddpages
        true

        print.print_orientation
        0

        print.print_page_delay
        50

        print.print_pagedelay
        500

        print.print_paper_data
        0

        print.print_paper_height
        11.00

        print.print_paper_size
        3407923

        print.print_paper_size_type
        1

        print.print_paper_size_unit
        0

        print.print_paper_width
        8.50

        print.print_printer

        print.print_reversed
        false

        print.print_scaling
        1.00

        print.print_shrink_to_fit
        true

        print.print_to_file
        false

        print.print_unwriteable_margin_bottom
        57

        print.print_unwriteable_margin_left
        25

        print.print_unwriteable_margin_right
        25

        print.print_unwriteable_margin_top
        25

        privacy.cpd.cookies
        false

        privacy.cpd.downloads
        false

        privacy.cpd.formdata
        false

        privacy.cpd.history
        false

        privacy.cpd.offlineApps
        true

        privacy.cpd.sessions
        false

        privacy.cpd.siteprefs
        false

        privacy.sanitize.migrateFx3Prefs
        true

        privacy.sanitize.timeSpan
        4

        security.warn_viewing_mixed
        false

  Graphics

        Adapter Description
        0x24200,0x20400

        WebGL Renderer
        Blocked for your operating system version.

        GPU Accelerated Windows
        0/1

    (In reply to Mats Palmgren [:mats] from comment #4)
> miceuz, does the problem still occur in Firefox 6?
> i don't have Firefox 6 right now, i'm on 7 beta channel

ok, even better.  Please submit the crash data and let us know the crash report ID:
https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report
(Reporter)

Comment 7

6 years ago
the crash does not get reported. 

i've tried this with older versions and with current beta - there is no information in about:crashes, no logs in ~/Library/Logs/CrashReporter and CrashReporter does not come up

maybe i could try with some special debugging - optimized version of firefox?
Maybe Firefox sees Cmd+ž as Cmd+Q for some reason?

Can you try creating a fresh profile for testing:
http://support.mozilla.com/en-US/kb/Managing-profiles
start firefox using this profile, open a new tab, load about:config in it,
click the "I'll be careful" button, type quit in the Filter box,
double click on browser.showQuitWarning to make it have the value true.
Make sure you have more than one tab open, then hit Cmd+ž.
Do you see the quit dialog?
> Maybe Firefox sees Cmd+ž as Cmd+Q for some reason?

Or more likely, as Cmd+Shift+w, which apparently means quit too.
(Reporter)

Comment 10

6 years ago
no, i've done as you've said, but FF just crashes on Cmd+ž
Created attachment 556861 [details]
stack

This is the stack trace I get under gdb with a Nightly build,
following STR in comment 0 and typing Cmd+w.

Updated

6 years ago
Keywords: stackwanted
> Failed to get CharCodes from EventRef

The crash seems to be triggered by this Objective-C exception.
What happens when you try comment #0's STR in other browsers, like Safari or Chrome?
In Chrome and Safari: Cmd+w and Cmd+Shift+w does nothing.
> In Chrome and Safari: Cmd+w and Cmd+Shift+w does nothing.

Do you see anything in the system console?  (Applications : Utilities : Console)
> In Chrome and Safari: Cmd+w and Cmd+Shift+w does nothing.

For me, that's actually also what happens in Firefox 6, Aurora and Nightly.
I'm on OSX 10.7 in case that matters.

> Do you see anything in the system console?

Yep, Chrome and Safari prints the same info as Firefox.

miceuz, does Chrome and/or Safari crash for you?
(Reporter)

Comment 17

6 years ago
(In reply to Mats Palmgren [:mats] from comment #16)
> miceuz, does Chrome and/or Safari crash for you?

no, neither Chrome nor Safari crashes
(Reporter)

Comment 18

6 years ago
From console:

Safari[131]: Failed to get CharCodes from EventRef (-9870)

firefox[139]: Mozilla has caught an Obj-C exception [NSInternalInconsistencyException: Failed to get CharCodes from EventRef (-9870)]
 
Google Chrome[158]: Failed to get CharCodes from EventRef (-9870)
Steven, do we have a pref or something to decide if we should abort on exceptions?

miceuz, what OSX version are you on?
(Reporter)

Comment 20

6 years ago
(In reply to Mats Palmgren [:mats] from comment #19)

> miceuz, what OSX version are you on?

10.5.8
> Steven, do we have a pref or something to decide if we should abort on exceptions?

We used to crash deliberately on *every* Objective-C exception, but that hasn't been true for a long time.  (In fact this change is what fixed bug 442245.)

But despite this, there appear to still be places where OS code can throw a fatal Objective-C exception.  We might be able to deal with this by wrapping calls to such code in an Objective-C exception handler that simply ignores the error and continues.

I'm probably the best one to deal with this ... though I've got a lot of more urgent bugs, and won't be able to get to it for a while.
Assignee: nobody → smichaud
Status: UNCONFIRMED → NEW
Ever confirmed: true
> I'm probably the best one to deal with this

Though I certainly don't want to prevent others from trying :-)
You need to log in before you can comment on or make changes to this bug.