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

Bug 319862

Summary: Mac Crash due to to Illegal Instruction
Product: [Eclipse Project] Platform Reporter: Jody Garnett <jody.garnett>
Component: SWTAssignee: Scott Kovatch <skovatch>
Status: CLOSED WONTFIX QA Contact: Silenio Quarti <Silenio_Quarti>
Severity: normal    
Priority: P3 CC: kubo, skovatch
Version: 3.6   
Target Milestone: ---   
Hardware: Macintosh   
OS: Mac OS X   
Whiteboard: stalebug
Attachments:
Description Flags
dialog produced by mac when JRE crashes
none
Crash produced using a tiled map
none
System Profile as per request (this seem large) none

Description Jody Garnett CLA 2010-07-14 10:44:38 EDT 
Build Identifier: Eclipse 3.6 

This problem was noticed when migrating to Eclispe 3.5.0 and the cocoa implementation of SWT. The RCP application uDig (http://udig.refractions.net/) has an optional tiled rendering system that crashes Java instantly when it is used on OSX.

I have been kind of hoping that this would be fixed as I update SWT; but after 3.5.0, 3.5.1, 3.5.2 and now 3.6.0 it is time to start trying to take this problem apart.

Reproducible: Always

Steps to Reproduce:
1. Download http://udig.refractions.net/files/downloads/udig-1.2-RC3.macosx.cocoa.x86.zip
2. Preferences > Renderer and place check next to tiled rendering
3. Display a map; there is a list of services providing maps on the "Web" view
Comment 1 Jody Garnett CLA 2010-07-14 10:47:18 EDT 
Created attachment 174296 [details]
dialog produced by mac when JRE crashes

I have tried this a number of times and the crash reports are always of this format.
Comment 2 Scott Kovatch CLA 2010-07-14 12:39:18 EDT 
Looks like we sent a null pointer into NSImage.drawInRect. I'll have a look.
Comment 3 Scott Kovatch CLA 2010-07-14 12:54:20 EDT 
I'm running 10.6.4 on a 15" Mac Book Pro with 4 GB of RAM and the tiled rendering doesn't crash for me. Can you attach a system profile of a machine that's crashing?
Comment 4 Jody Garnett CLA 2010-07-14 21:47:04 EDT 
That is the same macbook I use; I will go over and provide more detailed instructions when I am off work and have the machine in front of me.
Comment 5 Jody Garnett CLA 2010-07-15 08:44:43 EDT 
Okay let me try the instructions again:
1. Download udig-1.2-RC3.macosx.cocoa.x86.zip as indicated
2. unzip and run
3. Close the Welcome screen
4. Application menu > Preferences
6. Select the Rendering preference page
7. Check "Use Tiled Rendering System" and press OK
   (Sorry for the extra work we have this turned off because of the crash)
8. File > New > Map
9. Layer > Grid (to give the map something to draw)
10. Use the Pan tool to move the image .... crash

The crash produced is attached.
Comment 6 Jody Garnett CLA 2010-07-15 08:47:13 EDT 
Created attachment 174393 [details]
Crash produced using a tiled map
Comment 7 Jody Garnett CLA 2010-07-15 08:53:40 EDT 
Created attachment 174394 [details]
System Profile as per request (this seem large)
Comment 8 Jody Garnett CLA 2010-07-15 08:55:14 EDT 
I note that 1.2-RC3 mentioned above uses Eclipse 3.5.2.

To test a release that uses Eclipse 3.6 consider:
- http://udig.refractions.net/files/downloads/branches/udig-1.2-SNAPSHOT.macosx.cocoa.x86.zip
- http://udig.refractions.net/files/downloads/branches/udig-1.2-SNAPSHOT.macosx.cocoa.x86_64.zip
Comment 9 Scott Kovatch CLA 2010-07-15 12:00:34 EDT 
(In reply to comment #5)

> The crash produced is attached.

Yup, that did it for me. I crashed at the same spot. I'll have a look. 

Thanks for the steps to reproduce. I likely wouldn't have figured that out on my own. I opened up the Web view and imported data from one of the links.
Comment 10 Lars Vogel CLA 2019-11-14 03:43:29 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.