Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 353055

Summary: GPF in OS.GTK_ACCEL_LABEL_GET_ACCEL_STRING
Product: [Eclipse Project] Platform Reporter: Matt Lavin <matt_lavin>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: critical    
Priority: P3 CC: eclipse.felipe, remy.suen
Version: 4.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
A collection of Eclipse javacore files from the crashes
none
More javacore files none

Description Matt Lavin CLA 2011-07-25 20:15:43 EDT
Build Identifier: 

During regular use, Eclipse 3.7 crashes in OS.GTK_ACCEL_LABEL_GET_ACCEL_STRING.  I feel like I have seen this only since I started using Eclipse 3.7, but I upgraded to  Gnome 3 on Ubuntu 11.04 about the same time.  I quickly looked at the javacore files associated with the crashes, and they all seem to crash in approximately the same code path:

3XMTHREADINFO      "main" J9VMThread:0x09109D00, j9thread_t:0x090B2D74, java/lang/Thread:0x764BB920, state:R, prio=6
3XMTHREADINFO1            (native thread ID:0xB34, native priority:0x6, native policy:UNKNOWN)
3XMTHREADINFO2            (native stack address range from:0xB6D6D000, to:0xB756E000, size:0x801000)
3XMTHREADINFO3           Java callstack:
4XESTACKTRACE                at org/eclipse/swt/internal/gtk/OS.GTK_ACCEL_LABEL_GET_ACCEL_STRING(Native Method)
4XESTACKTRACE                at org/eclipse/swt/widgets/MenuItem.setText(MenuItem.java:882(Compiled Code))
4XESTACKTRACE                at org/eclipse/jface/action/ActionContributionItem.update(ActionContributionItem.java:935(Compiled Code))
4XESTACKTRACE                at org/eclipse/jface/action/ActionContributionItem$1.propertyChange(ActionContributionItem.java:113(Compiled Code))
4XESTACKTRACE                at org/eclipse/jface/action/ExternalActionManager$CommandCallback.bindingManagerChanged(ExternalActionManager.java:260(Compiled Code))
4XESTACKTRACE                at org/eclipse/jface/bindings/BindingManager.fireBindingManagerChanged(BindingManager.java:900(Compiled Code))
4XESTACKTRACE                at org/eclipse/jface/bindings/BindingManager.setActiveBindings(BindingManager.java:2176)
4XESTACKTRACE                at org/eclipse/jface/bindings/BindingManager.recomputeBindings(BindingManager.java:1742)
4XESTACKTRACE                at org/eclipse/jface/bindings/BindingManager.contextManagerChanged(BindingManager.java:689)
4XESTACKTRACE                at org/eclipse/core/commands/contexts/ContextManager.fireContextManagerChanged(ContextManager.java:165(Compiled Code))
4XESTACKTRACE                at org/eclipse/core/commands/contexts/ContextManager.setEventCaching(ContextManager.java:324(Compiled Code))
4XESTACKTRACE                at org/eclipse/core/commands/contexts/ContextManager.deferUpdates(ContextManager.java:83(Compiled Code))
4XESTACKTRACE                at org/eclipse/ui/internal/contexts/ContextAuthority.sourceChanged(ContextAuthority.java:673(Compiled Code))
4XESTACKTRACE                at org/eclipse/ui/internal/services/ExpressionAuthority.sourceChanged(ExpressionAuthority.java:310(Compiled Code))
4XESTACKTRACE                at org/eclipse/ui/internal/services/ExpressionAuthority.sourceChanged(ExpressionAuthority.java:279(Compiled Code))
4XESTACKTRACE                at org/eclipse/ui/AbstractSourceProvider.fireSourceChanged(AbstractSourceProvider.java:99(Compiled Code))

Reproducible: Sometimes

Steps to Reproduce:
Can't find steps to reproduce, but developing on Eclipse all day in my environment usually causes it to crash every other day or so.
Comment 1 Matt Lavin CLA 2011-07-25 20:21:16 EDT
Created attachment 200318 [details]
A collection of Eclipse javacore files from the crashes

Here are some javacore files from the recent crashes I've seen.
Comment 2 Matt Lavin CLA 2011-07-25 20:21:57 EDT
Created attachment 200319 [details]
More javacore files
Comment 3 Felipe Heidrich CLA 2011-07-26 11:58:45 EDT

*** This bug has been marked as a duplicate of bug 345979 ***