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

Bug 325238

Summary:	Crash on code assistant
Product:	[WebTools] JSDT	Reporter:	Henrique Haas <medelin>
Component:	General	Assignee:	Project Inbox <jsdt.javascript-inbox>
Status:	CLOSED DUPLICATE	QA Contact:	Nitin Dahyabhai <thatnitind>
Severity:	critical
Priority:	P3	CC:	cmjaun, ganoro, jacek.pospychala
Version:	3.2.1	Keywords:	needinfo
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Henrique Haas

2010-09-14 08:13:07 EDT

Build Identifier: 20100617-1415 

$ ./eclipse --sync
(running fine before crash - the crash occur just when the code assistant box tip get closed)
IMPLEMENT resolveForAllocation for class org.eclipse.wst.jsdt.internal.compiler.ast.ThisReference
IMPLEMENT resolveForAllocation for class org.eclipse.wst.jsdt.internal.compiler.ast.ThisReference
The program 'Eclipse' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
  (Details: serial 124033 error_code 158 request_code 148 minor_code 7)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


Reproducible: Always

Steps to Reproduce:
1. Typing and coding
2. A code assistant box will appear, perhaps suggesting a object attribute
3. Whenever box get closed (either by ESC, or whatever), the eclipse crash, and errors of "Details", given above, appear on my terminal.

Comment 1 Roy Ganor

2010-09-16 06:56:56 EDT

According to the error log, this issue belongs to the JSDT team,

thanks for reporting!

Comment 2 Chris Jaun

2010-09-16 10:30:20 EDT

Do you have some example code to reproduce this problem?

Comment 3 Henrique Haas

2010-09-16 10:41:19 EDT

The issue seems be related with PDT code assistant.
Any PHP code generates such problem, as follow:

1. Remember to keep the Code Assistant turned on (automatically) at PHP > Editor (preferences);
2. Code:

<?php
$dummy = 1;
$d (just type "d" and code assistant take action, offering you to complete with "dummy" word. Press <esc> and code assistant should exit, and then eclipse die)

Comment 4 Chris Jaun

2010-09-16 10:54:57 EDT

Do you have any JavaScript in your project?

Comment 5 Henrique Haas

2010-09-16 11:54:33 EDT

I have it, 3 files .js inside my project, not in php file.

Comment 6 Chris Jaun

2010-09-16 14:12:42 EDT

But you were not editing JavaScript when this crash occurred, correct?

The JSDT log message don't really indicate anything that would cause a crash to me.

Comment 7 Henrique Haas

2010-09-16 14:57:29 EDT

I was not editing the JS files.
The issue occurs whenever Code Assistant close, regardless if I have used its indication, or just press Esc to leave. This time, Eclipse suddenly closes.

Comment 8 Nitin Dahyabhai

2010-09-16 15:23:12 EDT

It might be a problem with your system configuration.  Which distribution are you on and what's it's version?  Which versions of Mozilla/Firefox/XulRunner are installed?  Which JRE are you using, and what's 32-bit and what's 64-bit?  Odds are this will have to be bounced to Platform IDE.

Comment 9 Henrique Haas

2010-09-16 15:32:10 EDT

Java Version:
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode)

Distribution: Ubuntu 10.04

Using Chrome: 6.0.472.55 beta

Eclipse 32-bit
CPU is Core 2 Duo 64-bit

Comment 10 Jacek Pospychala

2010-09-16 18:19:33 EDT

Henrique,
is there any file named hs_err_pid<number>.log in your Eclipse directory?
Asking because this reminds me of bug 322222

Comment 11 Nitin Dahyabhai

2010-09-29 18:12:26 EDT

Resolving as a duplicate of bug 322222 unless Henrique can give us more details.  Either way, I'm pretty sure its not something JSDT or PDT would be able to fix at our level.

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