Closed Bug 637618 Opened 14 years ago Closed 4 years ago

[10.6] crash in mozilla::gl::GLContextCGL::SwapBuffers @ AppleIntelGMAX3100GLDriver

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Platform:
x86_64
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
blocking2.0 --- -

People

(Reporter: scoobidiver, Unassigned)

References

Details

(Keywords: crash, Whiteboard: rdar://9182813 [platform-rel-Intel])

Crash Data

It is a new crash signature that first appeared in 4.0b12pre/20110222 soon after the fixing of bug 627656. It is #7 top crasher in 4.0b12 on Mac OS X. Signature GeForceGLDriver@0x12910 UUID 1be8eaca-d7bb-409f-9bec-685c42110228 Time 2011-02-28 21:27:58.101593 Uptime 299 Install Age 299 seconds (5.0 minutes) since version was first installed. Product Firefox Version 4.0b12 Build ID 20110222205430 Branch 2.0 OS Mac OS X OS Version 10.6.6 10J567 CPU amd64 CPU Info family 6 model 23 stepping 10 Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS Crash Address 0x0 User Comments I was scrolling while looking at the comments on a freinds facebook photo. It must have been too much. And it died. :( But I love the layout and am enjoying my first night on Beta. App Notes Renderers: 0x22600,0x20400 Frame Module Signature [Expand] Source 0 GeForceGLDriver GeForceGLDriver@0x12910 1 GeForceGLDriver GeForceGLDriver@0xd5786 2 @0x1ffffffff 3 GeForceGLDriver GeForceGLDriver@0xd5fc5 4 OpenGL OpenGL@0x324c 5 XUL mozilla::gl::GLContextCGL::SwapBuffers gfx/thebes/GLContextProviderCGL.mm:187 6 XUL mozilla::layers::LayerManagerOGL::Render gfx/layers/opengl/LayerManagerOGL.cpp:623 7 XUL mozilla::layers::LayerManagerOGL::EndTransaction gfx/layers/opengl/LayerManagerOGL.cpp:427 8 XUL nsDisplayList::PaintForFrame layout/base/nsDisplayList.cpp:541 9 XUL nsLayoutUtils::PaintFrame layout/base/nsLayoutUtils.cpp:1564 10 XUL PresShell::Paint layout/base/nsPresShell.cpp:6203 11 XUL nsViewManager::RenderViews view/src/nsViewManager.cpp:458 12 XUL nsViewManager::Refresh view/src/nsViewManager.cpp:424 13 XUL nsViewManager::DispatchEvent view/src/nsViewManager.cpp:925 14 XUL HandleEvent view/src/nsView.cpp:161 15 XUL nsChildView::DispatchEvent widget/src/cocoa/nsChildView.mm:1807 16 XUL nsChildView::DispatchWindowEvent widget/src/cocoa/nsChildView.mm:1817 17 XUL -[ChildView drawRect:inContext:] widget/src/cocoa/nsChildView.mm:2874 18 XUL -[ChildView drawRect:] widget/src/cocoa/nsChildView.mm:2780 19 AppKit AppKit@0x100cf8 20 AppKit AppKit@0xfbf6a 21 AppKit AppKit@0x73c5ff 22 AppKit AppKit@0xfb81f 23 Foundation Foundation@0x16bd9 24 AppKit AppKit@0x801aff 25 AppKit AppKit@0xfe4ce 26 libSystem.B.dylib libSystem.B.dylib@0xa2d8 27 libSystem.B.dylib libSystem.B.dylib@0xa2d8 28 AppKit AppKit@0x753197 29 AppKit AppKit@0x2379a 30 CoreFoundation CoreFoundation@0xbc24 31 CoreFoundation CoreFoundation@0x1052b 32 CoreFoundation CoreFoundation@0xfcd6 33 CoreFoundation CoreFoundation@0xfb2e 34 CoreFoundation CoreFoundation@0x24814 35 CoreFoundation CoreFoundation@0x24688 36 Foundation Foundation@0x14dbb 37 AppKit AppKit@0xfee59 38 libSystem.B.dylib libSystem.B.dylib@0xa2d8 39 AppKit AppKit@0x753197 40 AppKit AppKit@0x2379a 41 CoreFoundation CoreFoundation@0xbc24 42 CoreFoundation CoreFoundation@0x13e1a7 43 CoreFoundation CoreFoundation@0xfcd6 The regression range is: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=df4d35ffa99f&tochange=1da3405c74fd More reports at: https://crash-stats.mozilla.com/report/list?product=Firefox&range_value=4&range_unit=weeks&signature=GeForceGLDriver%400x12910
Joe/Benoit, can you please look and see if this is obviously caused by a recent change?
This is not obviously caused by a recent change. It's probably the case that we have corruption or some other bug that's causing this crash, and checking in bug 627656 just moved the crash around.
We need somebody to reproduce this in a debug build with MOZ_GL_DEBUG. Indeed, SwapBuffers is typically where the GL implementation flushes a lot of queued commands.
There's nothing obvious that I can see from URLs. It's all over the place afaict, including in about:home. Chris, do you see any commonalities?
nothing I can see that stands out. looks like general browsing with maybe gmail running off in a tab somewhere. here are some stats and some stuff to try. Correlation to startup or time of session 56 total crashes for GeForceGLDriver@0x12910 on 20110228-crashdata.csv 5 startup crashes inside 30 sec. 6 startup crashes inside 3 min. 5 repeated crashes inside 3 min. of last crash os breakdown GeForceGLDriver@0x12910Total 56 Win5.1 0.00 Win6.0 0.00 Win6.1 0.00 Mac10.4 0.00 Mac10.5 0.00 Mac10.6 1.00 55 0.982143 Mac OS X10.6.6 10J567 1 0.0178571 Mac OS X10.6.5 10H574 types of sites 42 http: 5 \N 4 jar:file: 3 https: 1 wyciwyg: 1 about:blank domains of sites 5 \N// 4 jar:file:// 4 http://www.facebook.com 3 http://www.youtube.com 2 http://www.flickr.com 2 http://www.amazon.com 2 http://static.ak.fbcdn.net 1 https://www.valuedopinions.com.au/index.php?id=17 1 https://hrbenefitsdirect.com/MAX 1 https://eximonline.exim.gov/bap/secBapLogoutHandler.do 1 http://www87.hattrick.org/Help/Rules/SetPiecesAndSpecial.aspx 1 http://www.zagolovki.ru/article/01Mar2011/sms 1 http://www.youtube.com/js/pyv_watch_request_ad.html 1 http://www.youtube.com/embed/dc6bKgado-0 1 http://www.youtube.com/ 1 http://www.tumblr.com/dashboard 1 http://www.seattlepi.com/forum/boards/viewtopic.asp?topicID=157781 1 http://www.restaurantlacoupole.com/index_english.html 1 http://www.reddit.com/r/pics/comments/ftzma/sorry_wrong_number_my_bad_nsfw/c1imvlb?context=1 1 http://www.readynas.com/forum/viewforum.php?f=10&sid=eec5b32c05c3ae0c80dd0731934f38aa 1 http://www.ndnation.com/boards/postform.php?backroom 1 http://www.ncbi.nlm.nih.gov.gate1.inist.fr/pubmed?term=bacterial%20universal%20stress%20protein%3A%20function%20and%20regulation. 1 http://www.lifenews.ru/news/52407 1 http://www.legacybangkok.com/weblet/relocate?FromURL=reslink&ToURL=%2Fz1038%2Fpromotions%2Ehtml 1 http://www.ilsole24ore.com/ 1 http://www.earthpatrolmedia.com/wordpress/?p=8110#more-8110 1 http://www.dr.dk/nu/live/?t 1 http://www.dhnet.be/ 1 http://www.dailytelegraph.com.au/lifestyle/sex-relationships/gynaecologists-recommend-abortion-safer-than-having-a-baby/story-e6frf01i-1226012964494 1 http://www.altrichmond.ca/gav.html 1 http://vancouver.ca/humanresources/jobs/index.htm 1 http://static.ak.fbcdn.net/connect/xd_proxy.php?version=0#cb=f9fdc0cfd5d63&origin=http%3A%2F%2Fwww.sport1.de%2Ffaeb53ccb32a24&relation=parent.parent&transport=postmessage&type=resize&height=28 1 http://static.ak.fbcdn.net/connect/xd_proxy.php?version=0#cb=f3c96a464f0a95a&origin=http%3A%2F%2Foscar.go.com%2Ff39a0ba216d274a&relation=parent.parent&transport=postmessage&type=resize&height=20&width=90 1 http://platform1.twitter.com/widgets/tweet_button.html?_=1298911413235&count=horizontal&lang=en&related=JackHerrick%3AFounder%20of%20wikiHow&text=How%20to%20Remix%20in%20Ableton%20Live&url=http%3A%2F%2Fwww.wikihow.com%2FRemix-in-Ableton-Live&via=wikiHow 1 http://nashtassia.tumblr.com/ 1 http://media.fastclick.net/w/safepop.cgi?cid=279352&mid=521588&sid=21908&c=45&ES=1140474264&EP=1131025012&UD=CQAAAAAAGJVAEQAAAGBeQFU-GQAAAEAzxDY-IRJ3BleKLnk-KAAwAA 1 http://ja.gram.pl/blog_komentarz_zapis.asp
It's possible that this is caused by other corruption elsewhere; for example, bug Brendan saw bug 633176, which manifested in the Firefox window turning black, but that was apparently fixed by bug 635968, which landed post-b12. Unfortunately we don't see these types of crashes very much in nightlies even at the best of times.
Unfortunately, we do have some crashes post-bug 635968, so this isn't fixed. :(
As painful as this is, I don't think we can block on it. Joe/Bjacob, please renominate as soon as you know something solid.
blocking2.0: ? → -
Chris, can you do a quick query to find emails for people with the signature GeForceGLDriver@0x12910 ? I've only found one, but it's super-difficult to query on crash-stats because loading lots of pages quickly seems to log me out.
This looks to also occur on Intel cards, though at a significantly lower rate than NVIDIA, for reasons that aren't entirely clear. Luckily, though, the Intel drivers on OS X do have symbols! It's not exactly the same stack trace, but I expect it's the same bug: (from bp-0098bbac-ae9a-48d6-b281-06eaf2110302) 0 AppleIntelGMAX3100GLDriver AppleIntelGMAX3100GLDriver@0xa1663 GHAL3D::CSurface2DResource::Delete(GHAL3D::CSurface2DResource*&) 1 AppleIntelGMAX3100GLDriver AppleIntelGMAX3100GLDriver@0x509d5 _i965UpdateTextureState 2 GLEngine GLEngine@0xd8672 _OffsetLimitImage3D 3 GLEngine GLEngine@0x154f3 _gliSetDispatch_CompExec 4 XUL _cairo_user_data_array_set_data gfx/cairo/cairo/src/cairo-array.c:486 5 GLEngine GLEngine@0xebac0 _gleUpdateFragmentFallbackProgram 6 GLEngine GLEngine@0x140b8d _gleUpdateVertexFallbackProgram 7 libSystem.B.dylib libSystem.B.dylib@0x6a02 8 AppleIntelGMAX3100GLDriver AppleIntelGMAX3100GLDriver@0x4d9ee _gldUpdateDispatch 9 GLEngine GLEngine@0xdd9b7 gleDoDrawDispatchCore 10 GLEngine GLEngine@0x23c52 gleSetEnable_FRAMGMENT_PROGRAM_ARB 11 GLEngine GLEngine@0x96ad3 gleDrawArraysOrElements_Entries_Body 12 GLEngine GLEngine@0x200e0 DrawArrays_Exec 13 libSystem.B.dylib libSystem.B.dylib@0x6a02 14 XUL mozilla::layers::ThebesLayerBufferOGL::RenderTo
(In reply to comment #9) > Chris, can you do a quick query to find emails for people with the signature > GeForceGLDriver@0x12910 ? here is a list of reports where we have e-mail provided for this sig for all the reports feb1-mar1 http://crash-stats.mozilla.com/report/index/021f65b1-73eb-47e8-8aea-f22152110203 4.0b9 GeForceGLDriver@0x12910 yes 20110203-crashdata.csv http://crash-stats.mozilla.com/report/index/c72d022f-2569-4365-be25-204cb2110203 4.0b10 GeForceGLDriver@0x12910 yes 20110203-crashdata.csv http://crash-stats.mozilla.com/report/index/8da80850-20d7-4ab2-85d6-73e812110208 4.0b10 GeForceGLDriver@0x12910 yes 20110208-crashdata.csv http://crash-stats.mozilla.com/report/index/102f5959-e129-4b69-a200-3874f2110208 4.0b10 GeForceGLDriver@0x12910 yes 20110208-crashdata.csv http://crash-stats.mozilla.com/report/index/fcbb4a8c-ce3b-4e11-8bc8-593942110209 4.0b10 GeForceGLDriver@0x12910 yes 20110209-crashdata.csv http://crash-stats.mozilla.com/report/index/1d0ee97e-e73c-478d-ad5e-72bfc2110209 4.0b10 GeForceGLDriver@0x12910 yes 20110209-crashdata.csv http://crash-stats.mozilla.com/report/index/efc44641-495f-4882-9f40-810a12110212 4.0b11 GeForceGLDriver@0x12910 yes 20110212-crashdata.csv http://crash-stats.mozilla.com/report/index/3921b10a-c2db-42fb-bfb9-4135c2110214 4.0b11 GeForceGLDriver@0x12910 yes 20110214-crashdata.csv http://crash-stats.mozilla.com/report/index/8dab0bc5-3a7d-4f6e-901c-5897c2110214 4.0b11 GeForceGLDriver@0x12910 yes 20110214-crashdata.csv http://crash-stats.mozilla.com/report/index/a2b9f350-a53b-423d-87bc-1778a2110215 4.0b10 GeForceGLDriver@0x12910 yes 20110215-crashdata.csv http://crash-stats.mozilla.com/report/index/952932bb-a922-40bd-b9f5-a05ca2110216 4.0b11 GeForceGLDriver@0x12910 yes 20110216-crashdata.csv http://crash-stats.mozilla.com/report/index/4fb318cb-231e-42a6-8904-94e2b2110217 4.0b10 GeForceGLDriver@0x12910 yes 20110217-crashdata.csv http://crash-stats.mozilla.com/report/index/1467e110-2fb0-4330-b361-86a562110217 4.0b11 GeForceGLDriver@0x12910 yes 20110217-crashdata.csv http://crash-stats.mozilla.com/report/index/b0ac1aca-0126-4aa9-8c20-52d1c2110217 4.0b11 GeForceGLDriver@0x12910 yes 20110217-crashdata.csv http://crash-stats.mozilla.com/report/index/82464d01-b7c3-45c3-b795-b62b72110218 4.0b11 GeForceGLDriver@0x12910 yes 20110218-crashdata.csv http://crash-stats.mozilla.com/report/index/88812b6b-52fe-4c11-b69e-cfe292110220 4.0b11 GeForceGLDriver@0x12910 yes 20110220-crashdata.csv http://crash-stats.mozilla.com/report/index/735f1b7f-d737-47fa-8fe7-9eb992110223 4.0b11 GeForceGLDriver@0x12910 yes 20110223-crashdata.csv http://crash-stats.mozilla.com/report/index/7c389067-e0ce-4183-bd5a-9ff022110224 4.0b11 GeForceGLDriver@0x12910 yes 20110224-crashdata.csv http://crash-stats.mozilla.com/report/index/c03e8cc8-0361-4d4a-9cc2-558ba2110228 4.0b11 GeForceGLDriver@0x12910 yes 20110228-crashdata.csv http://crash-stats.mozilla.com/report/index/3903963a-54c2-40c8-b275-a70052110301 4.0b12 GeForceGLDriver@0x12910 yes 20110301-crashdata.csv http://crash-stats.mozilla.com/report/index/ec22834e-59c8-46a4-83f4-fb9b82110301 4.0b12 GeForceGLDriver@0x12910 yes 20110301-crashdata.csv http://crash-stats.mozilla.com/report/index/e610a0d1-12ea-4ea3-8df4-8e8482110301 4.0b12 GeForceGLDriver@0x12910 yes 20110301-crashdata.csv http://crash-stats.mozilla.com/report/index/a5ad2b80-9d8c-4537-b285-c53042110301 4.0b12 GeForceGLDriver@0x12910 yes 20110301-crashdata.csv
Keywords: qawanted
It is #5 top crasher on Mac OS X in 4.0RC1.
Just ran into this with 2011-03-15 nightly. Do you guys need any extra info?
Were you doing anything in particular? Can you reproduce it? Have you seen it before, or since?
I was on http://mehdiisdumb.com/crossword/index.php (hit Play now to see the crossword..) and hit the space bar. When you hit the space bar on that page, the active bar flips direction. Before it crashed, I hit the space bar and the focus bar did not change, that is, the change was not drawn. Sadly, I can't reproduce it and have not ran across it before or since. Not sure if it's related but on that same page, I have noticed that after hitting the space bar, it will sometimes take a few seconds before anything is drawn on the page though all events are still handled.
Hmmm just ran into this again. Was on a different page and scrolling when it happened.
So, I've been disassembling the driver trying to figure out what's going on here. 0x200012900 <gldAttachDrawable+2512>: push %rbp 0x200012901 <gldAttachDrawable+2513>: mov %rsp,%rbp 0x200012904 <gldAttachDrawable+2516>: cmp $0xfff,%edi 0x20001290a <gldAttachDrawable+2522>: ja 0x200012910 <gldAttachDrawable+2528> 0x20001290c <gldAttachDrawable+2524>: mov %edi,%eax 0x20001290e <gldAttachDrawable+2526>: mov %edi,(%rax) 0x200012910 <gldAttachDrawable+2528>: mov %edi,0x0 0x200012917 <gldAttachDrawable+2535>: leaveq 0x200012918 <gldAttachDrawable+2536>: retq It looks like this is some type of run-time abort that does subtly different behaviour based on whether a particular value has a value greater than 4095 (0xfff). In particular, at 0x12910, where this crash is, there's an unconditional dereference of 0. There are a lot of limits of 4096 in GL; I'm not sure which this is. Having a minidump-to-core converter would *really* help in debugging this.
In the Intel driver, this code is located inside a function called _glrReturnUnexpectedKillClient that does things very much like the GeForce driver. _glrReturnUnexpectedKillClient: 000000000002a410 pushq %rbp 000000000002a411 movq %rsp,%rbp 000000000002a414 cmpl $0x00000fff,%edi 000000000002a41a ja 0x0002a420 000000000002a41c movl %edi,%eax 000000000002a41e movl %edi,(%rax) 000000000002a420 movl %edi,__mh_bundle_header 000000000002a427 leave 000000000002a428 ret 000000000002a429 nopl __mh_bundle_header(%rax)
Summary: Crash in mozilla::gl::GLContextCGL::SwapBuffers [@ GeForceGLDriver@0x12910 ] → Crash in mozilla::gl::GLContextCGL::SwapBuffers [@ GeForceGLDriver@0x12910 ] [@ AppleIntelGMAX3100GLDriver@0x2a420 ]
Looks like _IOConnectCallMethod is returning NULL/0: 000000000003c5ef callq 0x003adfd6 ; symbol stub for: _IOConnectCallMethod 000000000003c5f4 movq 0xa8(%rbp),%rbx 000000000003c5f8 testl %eax,%eax 000000000003c5fa je 0x0003c671 000000000003c5fc movl %eax,%edi 000000000003c5fe callq _glrKillClient Benoit Girard, do you know anything about IOConnectCallMethod?
Same as you probably already knew: It's a function part of IOKitLib used for programs (drivers too I suppose) to communicate with hardware: The IOKitLib, located in the I/O Kit framework, contains the generic I/O Kit functions you use to implement user-space task access to in-kernel device objects. http://developer.apple.com/library/mac/#documentation/DeviceDrivers/Conceptual/AccessingHardware/AH_IOKitLib_API/AH_IOKitLib_API.html I found a bit of documentation on the call in: /System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h
I filed a bug, rdar://9182813 , with Apple to find out what's going on here. I'd like Josh to use a DTS incident to find out whether we're causing this and what we can do about it.
Whiteboard: rdar://9182813
CC'ing Chris at Apple.
Crash Signature: [@ GeForceGLDriver@0x12910 ] [@ AppleIntelGMAX3100GLDriver@0x2a420 ]
There still seems to be some variant of this one around but in very low volume. Anything with a signature containing GeForceGLDriver appears on #100 on the mac top crash list. Removing the top crash keyword but will leave the bug open.
Crash Signature: [@ GeForceGLDriver@0x12910 ] [@ AppleIntelGMAX3100GLDriver@0x2a420 ] → [@ GeForceGLDriver@0x12910 ] [@ AppleIntelGMAX3100GLDriver@0x2a420 ]
Keywords: topcrash
Crash Signature: [@ GeForceGLDriver@0x12910 ] [@ AppleIntelGMAX3100GLDriver@0x2a420 ] → [@ GeForceGLDriver@0x12910 ] [@ AppleIntelGMAX3100GLDriver@0x2a420 ] [@ AppleIntelGMAX3100GLDriver@0x2a920 ] [@ GeForceGLDriver@0x12010 ]
Blocks: 605749
Blocks: 605779
If you look at https://crash-stats.mozilla.com/report/list?product=Firefox&signature=CheckMapHeaderCommon it appears one user is hitting a variant of this in 14.0.1.
Crash Signature: [@ GeForceGLDriver@0x12910 ] [@ AppleIntelGMAX3100GLDriver@0x2a420 ] [@ AppleIntelGMAX3100GLDriver@0x2a920 ] [@ GeForceGLDriver@0x12010 ] → [@ GeForceGLDriver@0x12910 ] [@ AppleIntelGMAX3100GLDriver@0x2a420 ] [@ AppleIntelGMAX3100GLDriver@0x2a920 ] [@ GeForceGLDriver@0x12010 ] [@ CheckMapHeaderCommon ]
It's #5 top crasher in 20.0 on Mac OS X. Almost all comments talk about Skype. More reports at: https://crash-stats.mozilla.com/report/list?signature=AppleIntelGMAX3100GLDriver%400x2a920 https://crash-stats.mozilla.com/report/list?signature=GeForceGLDriver%400x12010
Keywords: regression → topcrash
Summary: Crash in mozilla::gl::GLContextCGL::SwapBuffers [@ GeForceGLDriver@0x12910 ] [@ AppleIntelGMAX3100GLDriver@0x2a420 ] → [10.6] crash in mozilla::gl::GLContextCGL::SwapBuffers @ AppleIntelGMAX3100GLDriver
It's #4 top browser crasher in 20.0.1 and #1 in 21.0b3 on Mac OS X.
Is https://crash-stats.mozilla.com/report/index/05a3dfd0-a1d8-40f1-87b4-514b22130708 the same issue? Seems to be a recent uptick in Thunderbird.
Flags: needinfo?(scoobidiver)
(In reply to Wayne Mery (:wsmwk) from comment #27) > Is > https://crash-stats.mozilla.com/report/index/05a3dfd0-a1d8-40f1-87b4- > 514b22130708 the same issue? Seems to be a recent uptick in Thunderbird. Yes.
Flags: needinfo?(scoobidiver)
(In reply to Scoobidiver from comment #28) > (In reply to Wayne Mery (:wsmwk) from comment #27) > > Is > > https://crash-stats.mozilla.com/report/index/05a3dfd0-a1d8-40f1-87b4- > > 514b22130708 the same issue? Seems to be a recent uptick in Thunderbird. > Yes. is there a workaround? And why would there be (relatively) huge uptick for thunderbird?
(In reply to Wayne Mery (:wsmwk) from comment #29) > is there a workaround? Update to Mac OS X 10.7 or above. > And why would there be (relatively) huge uptick for thunderbird? Seems related to Skype so might be a link in an email.
I have this crash in both FF and TB, starting with a new, clean profile does not help. In fact, FF profile manager crashes itself. I have re-installed FF and TB multiple times, and completely removed Skype (using App Zapper) just to be sure. Is there really no other workaround other than upgrading my operating system? Needless to say, that's a non-starter just to be able to use FF or TB.
Removing topcrash keyword as this is #16 of all Firefox 23.0.1 MacOSX crashes and non-existent on Firefox 24b4. Eric, would you mind trying the latest Beta to see if this still reproduces for you? http://beta.mozilla.org
Keywords: topcrash
24b4 crashes the same way, unfortunately.
(In reply to Eric Rizzo from comment #33) > 24b4 crashes the same way, unfortunately. Eric, can you look up the crash ID for 24.0b4 via your about:crashes page? Would be helpful to see if the classification is the same or the signature morphed there.
Here it is: https://crash-stats.mozilla.com/report/index/852ad90e-cf46-4137-a458-c399e2130823 (In reply to Robert Kaiser (:kairo@mozilla.com) from comment #34) > (In reply to Eric Rizzo from comment #33) > > 24b4 crashes the same way, unfortunately. > > Eric, can you look up the crash ID for 24.0b4 via your about:crashes page? > Would be helpful to see if the classification is the same or the signature > morphed there.
Whiteboard: rdar://9182813 → rdar://9182813 [platform-rel-Intel]
platform-rel: --- → ?
platform-rel: ? → ---

Marking this as Resolved > Worksforme since there are no crashes with this signature reported in the last 6 months.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.