Community
Participate
Working Groups
Hi all, First thanks for all of your hard work on BIRT. It's really improved in terms of how smoothly everything works, lot's of subtle ways. I have a crashing bug in Cocoa that I've always thought was related to the early alpha driver I was using but I'm seeing it in a completely different driver so I think there is something else going on here. It's been happening at least since 2.6, but this is with 4.0.0.v20101209 in Indigo. This is what I'm seeing. I don't know if we would need to bring Cocoa UI team into this or not, but I thought that BIRT would be first place to take a look. Here's all of the stack trace, etc.. from Mac log. Process: eclipse [8171] Path: /Developer/eclipseM4/Eclipse.app/Contents/MacOS/eclipse Identifier: org.eclipse.eclipse Version: 3.6 (3.6) Code Type: X86-64 (Native) Parent Process: ??? [1] Date/Time: 2010-12-24 15:23:42.554 -0800 OS Version: Mac OS X 10.6.5 (10H574) Report Version: 6 Interval Since Last Report: 248276 sec Crashes Since Last Report: 1 Per-App Interval Since Last Report: 406966 sec Per-App Crashes Since Last Report: 1 Anonymous UUID: 4C6C39A9-EF2D-48B9-8576-64418C83B417 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: Java information: Exception type: Bus Error (0xa) at pc=7fff80f9f298 Java VM: Java HotSpot(TM) 64-Bit Server VM (17.1-b03-307 mixed mode macosx-amd64) Current thread (115000000): JavaThread "main" [_thread_in_native, id=1893055648, stack(7fff5f400000,7fff5fc00000)] Stack: [7fff5f400000,7fff5fc00000] Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j org.eclipse.swt.internal.cocoa.OS.objc_msgSend(JJJLorg/eclipse/swt/internal/cocoa/NSPoint;Lorg/eclipse/swt/internal/cocoa/NSSize;JJJZ)J+0 j org.eclipse.swt.internal.cocoa.NSView.dragImage(Lorg/eclipse/swt/internal/cocoa/NSImage;Lorg/eclipse/swt/internal/cocoa/NSPoint;Lorg/eclipse/swt/internal/cocoa/NSSize;Lorg/eclipse/swt/internal/cocoa/NSEvent;Lorg/eclipse/swt/internal/cocoa/NSPasteboard;Lorg/eclipse/swt/internal/cocoa/id;Z)V+65 j org.eclipse.swt.dnd.DragSource.drag(Lorg/eclipse/swt/widgets/Event;)V+310 j org.eclipse.swt.dnd.DragSource$1.handleEvent(Lorg/eclipse/swt/widgets/Event;)V+81 J org.eclipse.swt.widgets.EventTable.sendEvent(Lorg/eclipse/swt/widgets/Event;)V j org.eclipse.swt.widgets.Display.sendEvent(Lorg/eclipse/swt/widgets/EventTable;Lorg/eclipse/swt/widgets/Event;)V+24 j org.eclipse.swt.widgets.Widget.sendEvent(Lorg/eclipse/swt/widgets/Event;)V+9 J org.eclipse.swt.widgets.Display.runDeferredEvents()Z j org.eclipse.swt.widgets.Display.readAndDispatch()Z+125 j org.eclipse.ui.internal.Workbench.runEventLoop(Lorg/eclipse/jface/window/Window$IExceptionHandler;Lorg/eclipse/swt/widgets/Display;)V+9 j org.eclipse.ui.internal.Workbench.runUI()I+555 j org.eclipse.ui.internal.Workbench.access$4(Lorg/eclipse/ui/internal/Workbench;)I+1 j org.eclipse.ui.internal.Workbench$7.run()V+55 j org.eclipse.core.databinding.observable.Realm.runWithDefault(Lorg/eclipse/core/databinding/observable/Realm;Ljava/lang/Runnable;)V+12 j org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Lorg/eclipse/swt/widgets/Display;Lorg/eclipse/ui/application/WorkbenchAdvisor;)I+18 j org.eclipse.ui.PlatformUI.createAndRunWorkbench(Lorg/eclipse/swt/widgets/Display;Lorg/eclipse/ui/application/WorkbenchAdvisor;)I+2 j org.eclipse.ui.internal.ide.application.IDEApplication.start(Lorg/eclipse/equinox/app/IApplicationContext;)Ljava/lang/Object;+99 j org.eclipse.equinox.internal.app.EclipseAppHandle.run(Ljava/lang/Object;)Ljava/lang/Object;+135 j org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Ljava/lang/Object;)Ljava/lang/Object;+103 j org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Ljava/lang/Object;)Ljava/lang/Object;+29 j org.eclipse.core.runtime.adaptor.EclipseStarter.run(Ljava/lang/Object;)Ljava/lang/Object;+149 j org.eclipse.core.runtime.adaptor.EclipseStarter.run([Ljava/lang/String;Ljava/lang/Runnable;)Ljava/lang/Object;+183 v ~StubRoutines::call_stub j sun.reflect.NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+0 j sun.reflect.NativeMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+87 j sun.reflect.DelegatingMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+6 j java.lang.reflect.Method.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+161 j org.eclipse.equinox.launcher.Main.invokeFramework([Ljava/lang/String;[Ljava/net/URL;)V+211 j org.eclipse.equinox.launcher.Main.basicRun([Ljava/lang/String;)V+126 j org.eclipse.equinox.launcher.Main.run([Ljava/lang/String;)I+4 v ~StubRoutines::call_stub
Created attachment 185811 [details] OS X crash report
Could you attach the report design for us to reproduce? Does the report only crash on Cocoa platform? Does the "large chart" you mean refer it contains large set of data of just the large size?
(In reply to comment #2) > Could you attach the report design for us to reproduce? > > Does the report only crash on Cocoa platform? > > Does the "large chart" you mean refer it contains large set of data of just the > large size? I mean a very large data set. The issue *may* have something to do with the driver as well. I'm going to confirm this and then try to wrap up the dataset with the chart, but unfortunately I probably will not be able to get to it until after EclipseCon.
Hi guys, since I haven't been able to get back to the testing and it isn't really blocking any critical functionality, I'm going to makr it down to normal and try to get back to it in late March.
