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

Bug 90563

Summary: DBCS3.1:RHEL 4.0 critical failure when entering project/workspace name
Product: [Eclipse Project] Platform Reporter: Henry Huang <hhenry>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: critical    
Priority: P3 CC: camle, ccyang, daniel_megert, steven.wasleski, Tod_Creasey, ycpeng
Version: 3.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux-GTK   
Whiteboard:
Attachments:
Description Flags
zip contains 2 error logs and one screen capture none

Description Henry Huang CLA 2005-04-06 23:51:17 EDT 
While testing under Red Hat Linux, in both Korean and Traditional Chinese, we 
encountered this problem:

When a Simple Project is created with the wizard, if the user enters the 
Project Name using the Red Hat input method for Korean, and then presses Enter,
the Eclipse application exits with an exception message.  Error data appears in 
both a local directory file and an exception message dialog.  The user can 
avoid the problem by using the mouse to click the "Finish" button, but if the 
user presses Enter instead, Eclipse exits with an exception.

At the final point in the dialog before Eclipse crashes, the "Next" button is 
disabled and the "Finish" button is enabled.  Under normal circumstances, both 
of these buttons are enabled, and pressing either "Next" or "Finish" results in 
normal operation.  However, in this case, only "Finish" is enabled, and 
pressing Enter results in the exception.

The problem also occurs while using the Red Hat input method for Traditional 
Chinese (Chang Jie), and for both languages while choosing a workspace at the 
opening prompt.
Comment 1 Henry Huang CLA 2005-04-07 01:10:25 EDT 
OS:	RHEL 4.0 
Language:	Korean/Traditional Chinese
Build level: 	M6
JDK version:  IBM JDK 1.4.2
Test case #: 1.1 and 11.2  

Summary: DBCS31:RHEL 4.0 critical failure when entering project/workspace name

Steps to recreate problem:
1-Launch Eclipse inside RHEL 4.0 Korean or Traditional Chinese
2-Use the built-in input method to enter a Korean or Traditional Chinese 
workspace name (using ChangJie for Traditional Chinese)
3-Press Enter

Alternate method:
1-Start the Create New Project Wizard
2-Choose Simple Project, and use the built-in input method to enter a Korean or 
Traditional Chinese project name (using ChangJie for Traditional Chinese)
3-Press Enter
Comment 2 Dani Megert CLA 2005-04-07 04:17:53 EDT 
>Error data appears in 
>both a local directory file and an exception message dialog
Can you please attach the log and a picture of the dialog.
Comment 3 Henry Huang CLA 2005-04-07 06:07:20 EDT 
Created attachment 19644 [details]
zip contains 2 error logs and one screen capture

.png file is a screen capture from Red Hat Linux
javacore.20050407.164319.12611.txt is automatically generated
jvmdump.txt was copied and pasted from the Linux shell into an editor
Comment 4 Henry Huang CLA 2005-04-07 06:14:15 EDT 
(In reply to comment #1)
> OS:	RHEL 4.0 
> Language:	Korean/Traditional Chinese
> Build level: 	M6
> JDK version:  IBM JDK 1.4.2
> Test case #: 1.1 and 11.2  
> Summary: DBCS31:RHEL 4.0 critical failure when entering project/workspace name
> Steps to recreate problem:
> 1-Launch Eclipse inside RHEL 4.0 Korean or Traditional Chinese
> 2-Use the built-in input method to enter a Korean or Traditional Chinese 
> workspace name (using ChangJie for Traditional Chinese)
> 3-Press Enter
> Alternate method:
> 1-Start the Create New Project Wizard
> 2-Choose Simple Project, and use the built-in input method to enter a Korean 
or 
> Traditional Chinese project name (using ChangJie for Traditional Chinese)
> 3-Press Enter

Method #3:
1-Open the Find/Replace Window
2-Enter Korean characters in the Find textbox
3-Press Enter (from the keyboard)
4-Press the Close button in the Window
Comment 5 Douglas Pollock CLA 2005-04-08 15:29:09 EDT 
The top of the thread dump is:
2XMFULLTHDDUMP Full thread dump J9SE VM (J2RE 1.4.2 IBM J9 2.2 Linux x86-32
build 20040916_0910_lHdSMR, native threads):

3XMTHREADINFO      "main" (TID:0x08069000, sys_thread_t:0x0805442C, state:R,
native ID:0x0805445C) prio=6

4XESTACKTRACE          at
org/eclipse/swt/internal/gtk/OS._gtk_widget_destroy(Native Method)

4XESTACKTRACE          at
org/eclipse/swt/internal/gtk/OS.gtk_widget_destroy(OS.java:6855)

4XESTACKTRACE          at
org/eclipse/swt/widgets/Widget.destroyWidget(Widget.java:362)

4XESTACKTRACE          at org/eclipse/swt/widgets/Widget.dispose(Widget.java:398)

4XESTACKTRACE          at org/eclipse/swt/widgets/Shell.dispose(Shell.java:1463)

4XESTACKTRACE          at org/eclipse/jface/window/Window.close(Window.java:321)

4XESTACKTRACE          at org/eclipse/jface/dialogs/Dialog.close(Dialog.java:891)

4XESTACKTRACE          at
org/eclipse/jface/dialogs/Dialog.okPressed(Dialog.java:856)

4XESTACKTRACE          at
org/eclipse/ui/internal/ide/ChooseWorkspaceDialog.okPressed(ChooseWorkspaceDialog.java:156)

4XESTACKTRACE          at
org/eclipse/jface/dialogs/Dialog.buttonPressed(Dialog.java:409)

4XESTACKTRACE          at
org/eclipse/jface/dialogs/Dialog$2.widgetSelected(Dialog.java:556)

4XESTACKTRACE          at
org/eclipse/swt/widgets/TypedListener.handleEvent(TypedListener.java:89)

4XESTACKTRACE          at
org/eclipse/swt/widgets/EventTable.sendEvent(EventTable.java:82)

4XESTACKTRACE          at org/eclipse/swt/widgets/Widget.sendEvent(Widget.java:1012)

4XESTACKTRACE          at
org/eclipse/swt/widgets/Display.runDeferredEvents(Display.java:2778)

4XESTACKTRACE          at
org/eclipse/swt/widgets/Display.readAndDispatch(Display.java:2472)
Comment 6 Felipe Heidrich CLA 2005-04-08 17:00:41 EDT 
From the stacktrace:
Module: /usr/lib/libglib-2.0.so.0
Module_base_address: 00101000
Symbol: g_mem_chunk_free

The GPF happened during destroy widget.



*** This bug has been marked as a duplicate of 89720 ***
Comment 7 Henry Huang CLA 2005-05-27 03:10:00 EDT 
Successful test result with build 20050526_1200