Closed Bug 475040 Opened 16 years ago Closed 16 years ago

Crash [@ nsObjCExceptionLogAbort], doing a 2 finger swipe on macbookpro

Categories

(Core :: Widget: Cocoa, defect)

Product:
Core
Component:
Widget: Cocoa
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: tchung, Assigned: smichaud)

Details

(Keywords: crash, Whiteboard: [needs input from Tony])

Crash Data

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090123 Minefield/3.2a1pre Build Identifier: This is not 100% reproducible, but it crashes on occasion when i'm on a page doing a 2 finger swipe to scroll down the page. Crash report on branch: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090123 Shiretoko/3.1b3pre - http://crash-stats.mozilla.com/report/index/6cac9ba7-acbd-4556-ade2-af6632090123 Crash report on trunk: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090122 Minefield/3.2a1pre - http://crash-stats.mozilla.com/report/index/7e2d1869-0259-4d67-a710-8c6a12090122 Stack Trace Frame Module Signature [Expand] Source 0 XUL nsObjCExceptionLogAbort nsObjCExceptions.h:152 1 XUL -[ChildView scrollWheel:forAxis:] widget/src/cocoa/nsChildView.mm:4094 2 XUL -[ChildView scrollWheel:] widget/src/cocoa/nsChildView.mm:4114 3 AppKit AppKit@0x10f6fc 4 XUL -[NSWindow nsCocoaWindow_NSWindow_sendEvent:] widget/src/cocoa/nsCocoaWindow.mm:2153 5 XUL -[ToolbarWindow sendEvent:] widget/src/cocoa/nsCocoaWindow.mm:1912 6 AppKit AppKit@0xdb713 7 AppKit AppKit@0x390f8 8 XUL nsAppShell::Run widget/src/cocoa/nsAppShell.mm:693 9 XUL nsAppStartup::Run toolkit/components/startup/src/nsAppStartup.cpp:192 10 XUL XRE_main toolkit/xre/nsAppRunner.cpp:3210 11 firefox-bin main browser/app/nsBrowserApp.cpp:156 12 firefox-bin firefox-bin@0x1541 13 firefox-bin firefox-bin@0x1468 14 @0x4 Reproducible: Always Steps to Reproduce: 1. open clean profile, either branch or trunk nightly build 2. enable 2 finger swipe on mac 3. visit a page where it requires you to scroll down a page (i was reading a bugzilla bug) 4. Crash, and crash reporter appears Actual Results: crashed while 2 finger swiping Expected Results: no crash please.
Flags: blocking1.9.1?
Keywords: crash
Version: unspecified → Trunk
Tony, please go into your console.log after reproducing this and find the exception listed there.
I believe this is the relevant log around the time the crash happened on branch. 1/23/09 9:29:53 AM [0x0-0x207207].org.mozilla.firefox Fri Jan 23 09:29:53 TchungMBP.local firefox-bin[24037] <Warning>: CGSResolveShmemReference : reference offset (36016) exceeds bounds (32768) on shmem obj 0x21216 1/23/09 9:29:53 AM [0x0-0x207207].org.mozilla.firefox 2009-01-23 09:29:53.705 firefox-bin[24037:10b] Mozilla has caught an Obj-C exception [NSInternalInconsistencyException: Error (1000) creating CGSWindow]
These (the errors from your system console) are the same ones you reported at bug 470864. I'm beginning to wonder if your MacBookPro is ill, or if you don't have much RAM in it, or if you're squeezing a lot of programs into however much RAM you have.
I also wonder if you see the same errors trying to do similar things in Safari. In any case, though, Firefox (probably) shouldn't crash on these errors. And I'm quite sure Safari doesn't.
Assignee: joshmoz → smichaud
not sure its a hardware problem. Running osx 10.5.2, 2.5Ghz Intel core 2 duo, with 4 Gb 667 Mhz DDR2 SDRAM. I also dont ever use Safari, so its never running. The errors shown probably are related, but the stack trace isn't? Anyway, i'll keep trying to narrow this down to a solid repro and comment as soon as i can.
(In reply to comment #5) > not sure its a hardware problem Neither am I sure that it *is* a hardware problem. But that's certainly possible. > I also dont ever use Safari Please start doing so :-) We need to see if the same kinds of errors happen in Safari. > i'll keep trying to narrow this down to a solid repro and comment as > soon as i can Thanks in advance!
(Following up comment #6) >> I also dont ever use Safari > > Please start doing so :-) We need to see if the same kinds of errors > happen in Safari. I mean the CGSResolveShmemReference and "Error (1000) creating CGSWindow" errors. I'm quite sure Safari won't crash, even if those errors happen while it's running.
Need more info on reproducibility and the number of people this is likely to affect before we can block.
Flags: blocking1.9.1? → blocking1.9.1-
here's another crash stack and console.log from yesterday. Sorry i can't still seem to find a solid repro or testcase just yet... http://crash-stats.mozilla.com/report/index/3851760b-41de-4f3d-be79-009782090125 1/25/09 3:55:13 PM firefox-bin[25389] Mozilla has caught an Obj-C exception [NSInternalInconsistencyException: Error (1000) creating CGSWindow] 1/25/09 3:54:17 PM [0x0-0x352352].org.mozilla.firefox Sun Jan 25 15:54:17 TchungMBP.local firefox-bin[25389] <Warning>: CGSResolveShmemReference : reference offset (36976) exceeds bounds (32768) on shmem obj 0x21216 1/25/09 3:55:13 PM [0x0-0x352352].org.mozilla.firefox Sun Jan 25 15:55:13 TchungMBP.local firefox-bin[25389] <Warning>: CGSResolveShmemReference : reference offset (36896) exceeds bounds (32768) on shmem obj 0x21216 1/25/09 3:55:13 PM [0x0-0x352352].org.mozilla.firefox 2009-01-25 15:55:13.307 firefox-bin[25389:10b] Mozilla has caught an Obj-C exception [NSInternalInconsistencyException: Error (1000) creating CGSWindow]
I use this way of scrolling all the time since I have a MacBook and never run into this problem. Happened it once again? Probably with a special profile?
Tony, are you still seeing this? The stack links are all gone :(
Whiteboard: [needs input from Tony]
That's because we stopped making all objc exceptions fatal. See bug 486574.
Sounds FIXED to me, then.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
i havent seen this in the last 6 months. Resolving WFM
Resolution: FIXED → WORKSFORME
Crash Signature: [@ nsObjCExceptionLogAbort]
You need to log in before you can comment on or make changes to this bug.