Comment 1 Grant Gayed 2004-03-26 13:33:06 EST

Are there any steps that consistently make this happen?  Or does it happen for 
you at startup?

Comment 2 Ron Yang 2004-03-26 14:19:29 EST

Hi, here's more info.  The crash happens when the editor needs to scroll.

One workflow to cause it:
1. unzip eclipse distribution into clean dir
2. start it, accept default options
3. new java project
4. new java class
5. paste in java source code that is taller than the editor and would require 
it to scroll
6. crashes


Workflow I had been following:
1. unzip eclipse distribution into clean dir
2. start it, accept default options
3. import existing java project
4. open any java file (java editor) or jsp file (text editor)
5. use mousewheel or page down to scroll the editor
6. crashes


Workflow that does not cause the crash:
1. unzip eclipse distribution into clean dir
2. start it, accept default options
3. new java project
4. new java class
5. type a single-line comment in the body of the new class
6. cut and paste the line so the file is taller than the editor
7. scroll up and down, no crash

This integration build: 200403220800 does not exhibit this crashing behavior 
for me.


Thanks,
Ron


Here's what I think is a slightly different crash stack:
---------------------------------------------
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at 
PC=0x74785F52
Function=ScriptApplyDigitSubstitution+0x12D0
Library=C:\WINDOWS\system32\USP10.dll

Current Java thread:
	at org.eclipse.swt.internal.win32.OS.ScriptTextOut(Native Method)
	at org.eclipse.swt.graphics.TextLayout.draw(TextLayout.java:470)
	at org.eclipse.swt.graphics.TextLayout.draw(TextLayout.java:339)
	at org.eclipse.swt.custom.StyledTextRenderer.drawLine
(StyledTextRenderer.java:133)
	at org.eclipse.swt.custom.StyledText.performPaint(StyledText.java:5637)
	at org.eclipse.swt.custom.StyledText.handlePaint(StyledText.java:5041)
	at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:4725)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:769)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:793)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:778)
	at org.eclipse.swt.widgets.Composite.WM_PAINT(Composite.java:781)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:2994)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:3146)
	at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method)
	at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:1374)
	at org.eclipse.swt.internal.BidiUtil.windowProc(BidiUtil.java:647)
	at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1450)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2254)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1562)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1536)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench
(Workbench.java:257)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:139)
	at org.eclipse.ui.internal.ide.IDEApplication.run
(IDEApplication.java:90)
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run
(PlatformActivator.java:277)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:239)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:117)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:316)
	at org.eclipse.core.launcher.Main.run(Main.java:741)
	at org.eclipse.core.launcher.Main.main(Main.java:725)

Comment 3 Steve Northover 2004-03-26 14:53:52 EST

FH to investigate.

Comment 4 Felipe Heidrich 2004-03-26 15:02:22 EST

We could not reproduce this. What locale are you running? Does the text has 
characters other than english (ANSI)? Does the build I200403260800 has the 
problem?

Comment 5 Ron Yang 2004-03-26 17:34:54 EST

Hi, turns out this is kind of my bad -- I'm a beta tester for xp sp2, and the 
segfault is in their code and the version info shows that this is a new version 
1.0420.2600.2096 (xpsp_sp2_rc1.040311-2315)

I'm going to try uninstalling sp2rc1 which will almost assuredly fix this issue.

I'm also create a new issue on windowsbeta

Thanks for your time,
Ron

Comment 6 Felipe Heidrich 2004-03-26 18:03:39 EST

please reopen this problem report case it happens to you on a stable version 
of Windows, thanks.

Comment 7 Felipe Heidrich 2004-03-30 10:59:14 EST

*** Bug 56487 has been marked as a duplicate of this bug. ***

Comment 8 Felipe Heidrich 2004-04-01 14:15:00 EST

*** Bug 56972 has been marked as a duplicate of this bug. ***

Comment 9 Grant Gayed 2004-04-02 10:13:36 EST

*** Bug 56777 has been marked as a duplicate of this bug. ***

Comment 10 Michael Giroux 2004-04-02 16:28:59 EST

I filed a bug report with MS on this.  It seems that the problem is that prior
to XP PRO SP2, ScriptTextOut did not validate a psc parameter.  In SP2, the psc
parameter is being checked "in order to check for OpenType地ess of the font for
the purpose of split call to OpenType drawing function, and it crashes because
*psc contains bogus data."  I'm not familiar with the API in question, so this
is the best lead I can provide.

Michael

Comment 11 Grant Gayed 2004-04-06 12:06:47 EDT

*** Bug 57476 has been marked as a duplicate of this bug. ***

Comment 12 Grant Gayed 2004-04-06 17:32:46 EDT

reopening report since swt may need to do something here

Comment 13 Grant Gayed 2004-04-07 17:21:19 EDT

*** Bug 57796 has been marked as a duplicate of this bug. ***

Comment 14 Felipe Heidrich 2004-04-08 17:53:04 EDT

I can't be 100% sure (I don't have Xp Service Pack 2) it is the same problem 
but we fixed a crash this week related with Uniscribe. 
Please, download next week integration build and retest. Reopen the problem 
report if the bug persist.

Comment 15 Grant Gayed 2004-04-12 11:18:36 EDT

*** Bug 58056 has been marked as a duplicate of this bug. ***

Comment 16 anubis 2004-04-13 00:55:43 EDT

*** Bug 58116 has been marked as a duplicate of this bug. ***

Comment 17 Michael Giroux 2004-04-13 14:10:05 EDT

Downloaded 3.0 Stream Integration Build I20040413.

So far, it appears the problem is resolved.  I'll open a new bug report if it
occurs again on this build.

Comment 18 Felipe Heidrich 2004-04-23 16:20:58 EDT

*** Bug 57301 has been marked as a duplicate of this bug. ***

Comment 19 Grant Gayed 2004-04-28 08:54:52 EDT

*** Bug 60096 has been marked as a duplicate of this bug. ***

Comment 20 Grant Gayed 2004-05-12 09:36:36 EDT

*** Bug 61857 has been marked as a duplicate of this bug. ***

Comment 21 Rafael Chaves 2004-05-12 11:13:15 EDT

*** Bug 61910 has been marked as a duplicate of this bug. ***

Comment 22 Grant Gayed 2004-05-12 17:30:43 EDT

*** Bug 61912 has been marked as a duplicate of this bug. ***

Comment 23 Grant Gayed 2004-05-13 10:06:51 EDT

*** Bug 62059 has been marked as a duplicate of this bug. ***

Comment 24 Felipe Heidrich 2004-08-23 15:21:55 EDT

*** Bug 71829 has been marked as a duplicate of this bug. ***

Comment 25 Felipe Heidrich 2004-09-01 18:26:56 EDT

Does anyone know if Microsoft got this bug fixed for SP 2 final release ?

Comment 26 Grant Gayed 2004-09-16 15:03:16 EDT

*** Bug 74072 has been marked as a duplicate of this bug. ***

Comment 27 Felipe Heidrich 2004-09-16 15:10:51 EDT

Does anyone know if Microsoft got this bug fixed for SP 2 final release ?

If people are having this crash on SP2 final release we will need to do 
something about it.

Comment 28 Victoria Morris 2004-09-16 15:45:53 EDT

I have Installed XP SP2 final release, and I have this problem.
I do not understand what the fix is.

Comment 29 Duane Bronson 2004-09-16 15:48:42 EDT

I have seen this problem in SP2 final release, but it says this was resolved.
My bug report was DUPE'd to 56390: https://bugs.eclipse.org/bugs/show_bug.cgi?
id=71829

I'm currently using a workaround where I place the old Windows\System32\USP10.
DLL in my eclipse startup directory.

Comment 30 Felipe Heidrich 2004-09-16 16:13:26 EDT

Resolution is wrong, it should be WONTFIX (given this is MS bug) but I will 
leave this problem open cause the final release is bad.

Comment 31 Michael Giroux 2004-09-16 16:18:46 EDT

See comment #10.  When I filed a bug w/ MS the response indicated that this 
was a permanent change in the API, and not a bug.

Comment 32 Felipe Heidrich 2004-09-16 17:17:49 EDT

Michael, can you give us more information, maybe copy more information from 
the MS bug and paste here.

Comment 33 Victoria Morris 2004-09-17 11:12:43 EDT

Here is the guts of the reponse I recieved from Microsoft:
-----------------------------------------

Based on my knowledge, this issue is most likely caused by the incompatibility 
of the Eclipse program with Service Pack 2. Now, I would like to provide the 
following two suggestions:

Suggestion 1: Temporarily give up your Eclipse and wait for the hotfix from 
the Eclipse.

Suggestion 2: Uninstall Service Pack 2 from your computer. I suggest we 
uninstall Service Pack 2 from your computer. You can use one of the following 
methods to uninstall Service Pack 2.

---------------------------------------------

Comment 34 Michael Giroux 2004-09-17 11:41:11 EDT

In reply to comment #32, following is the extent of what MS told me about the 
problem I reported.  This specific problem seems to have been resolved because 
my Eclipse 3.0 no lnoger crashes.  However, this bug may actually be covering 
more than one case.  From the MS comment below, it would appear that it is 
necessary to review any Eclipse code that invokes drawing functions to make 
sure they are passing in valid parameters.

The fact that some are still having this problem, and others (me) are not 
suggests (to me) that a plugin may be involved.

"in order to check for OpenType地ess of the font for
the purpose of split call to OpenType drawing function, and it crashes because
*psc contains bogus data."

Comment 35 Michael Giroux 2004-09-20 11:31:20 EDT

Following is the entire reply from MS on this. -- Michael
--------------------------------------------------


FYI Michael: 
*************************************** 
  
Problem Description: 
  
This Microsoft Windows XP Professional issue always happens and I don't know 
if this issue existed previously.  This install is an upgrade from Windows XP.
  
Running eclipse workbench version 3.0 milestone 8 (3.0 M8) I am getting a 
fault in USP10.dll. 
4/2/2004 12:18 PM       
Sent: April 01, 2004 01:25 PM 
= 
Subject: RE: Two beta reprots about AV on USP10.DLL 
The ELK check-in in SP2 seems to introduce a new code path in ScriptTextOut 
that calls ScriptCheckCache and crashes in this case.
Strictly speaking, this is not an OS bug. The app is not supposed to pass in a 
bogus psc to ScriptTextOut. It’s just that we never care before. The ELK 
change introduces this call in order to check for OpenType’ness of the font 
for the purpose of split call to OpenType drawing function, and it crashes 
because *psc contains bogus data.
For this particular customer, we should let them know that they have bug in 
their code that leads to a corrupted *psc either due to uninitialized data 
structure or buffer overrun and the way to fix this is to make sure that the 
passing *psc is either null or remains valid. 

Comment 36 Georg Steigmeier 2004-09-23 04:51:51 EDT

I also encountered this problem after installing XP SP2 (eclipse crashes during 
scrolling in a source file), that was with eclipse platform 3.0.0. After 
installing eclipse platform 3.0.1 it works fine again; but this probably also 
could be because of the different eclipse configuration or because of new 
plugins that is use.

Comment 37 Grant Gayed 2004-09-30 11:40:31 EDT

*** Bug 75393 has been marked as a duplicate of this bug. ***

Comment 38 Felipe Heidrich 2004-09-30 12:32:40 EDT

I'm using the ddl from bug 71829, which is a "bad" version of usp10.dll.
But still I can't recreate the crash using the steps described in comment#2, 
could you guys let me know what font you use ? Or export and attach here your 
preference pages. Thanks.

Comment 39 Felipe Heidrich 2004-11-05 11:46:37 EST

*** Bug 77828 has been marked as a duplicate of this bug. ***

Comment 40 Felipe Heidrich 2005-04-21 11:51:34 EDT

*** Bug 92034 has been marked as a duplicate of this bug. ***

Comment 41 Amarjeet Singh 2005-05-24 03:10:33 EDT

(In reply to comment #36)
> I also encountered this problem after installing XP SP2 (eclipse crashes during 
> scrolling in a source file), that was with eclipse platform 3.0.0. After 
> installing eclipse platform 3.0.1 it works fine again; but this probably also 
> could be because of the different eclipse configuration or because of new 
> plugins that is use.

It now has become perplexing to the team working with me as the organization
polivy forced us to upgrade to SP2 on WinXP boxes and most of the developers are
screaming at the frequency at which Eclipse crashes whenever there is a scroll
action on either a source file opened or on any other kind of a file.

Here is the description of my environment:
OS: Microsoft XP SP2
RAM: 1.5 GB
Processor: P4 2.8 Ghz HT
Eclipse Build: Version: 3.0.0
Build id: 200403261517

Stack trace in the PID log is similar to the ones added by others previously.

Is there a workaround, apart from downgrading XP back to SP1, as this is no more
an option for us? It has really become critical as the whole project is closely
integrated with Eclipse 3.0 and I am not willing to spend time trying to
configure an 8000+ classes project into NetBeans :-(

Comment 42 Felipe Heidrich 2005-05-24 11:29:07 EDT

Amarjeet, you can use the workaround described on comment #29.

Please, let me know what is the font and the system locale you are using with 
Eclipse.

Comment 43 Felipe Heidrich 2005-05-27 11:58:03 EDT

*** Bug 96909 has been marked as a duplicate of this bug. ***

Comment 44 Felipe Heidrich 2005-06-07 10:37:07 EDT

*** Bug 97410 has been marked as a duplicate of this bug. ***

Comment 45 Felipe Heidrich 2005-08-18 11:38:32 EDT

*** Bug 107319 has been marked as a duplicate of this bug. ***

Comment 46 Felipe Heidrich 2005-08-18 12:05:55 EDT

Could someone please tell me what font is being used at the time of the crash?

Comment 47 Chris A. McNeil 2005-10-05 12:06:11 EDT

The fix referenced by comment #29 did not work for me.  Our shop forced an 
upgrade to XP SP2 this morning and I started encountering this error (version 
3.0.0 Build 200403261517).  Since I start Eclipse using the -vm parameter, 
pointing to a specific JDK, I needed to place the old (SP1) copy of usp10.dll 
in the JDK /bin directory (where java.exe resides) rather than in the Eclipse 
startup directory.

Comment 48 Billy Biggs 2005-11-28 19:59:22 EST

*** Bug 118333 has been marked as a duplicate of this bug. ***

Comment 49 Steve Northover 2006-04-05 12:42:22 EDT

FH, anything new on this?  Can we call ScriptTextOut() with different parameters?

Comment 50 Michael Giroux 2006-04-05 12:48:35 EDT

(In reply to comment #49)

See comment #10.  Based on input from Microsoft, the API now (since XP SP2) requires that all parameters be valid.

Comment 51 Felipe Heidrich 2006-08-02 11:23:11 EDT

*** Bug 152442 has been marked as a duplicate of this bug. ***

Comment 52 Guy Melançon 2007-01-08 10:58:30 EST

(In reply to comment #51)
> *** Bug 152442 has been marked as a duplicate of this bug. ***

I am experiencing the same JVM crash on a fresh install of both Win XP SP2 and Eclipse 3.2.1. I did not see any fix suggested in this thread. The fact that nobody replied since last August made me think you had the impression the bug was fixed somehow (I must admit I can not interpret comment #49).

I crash when I try to create a project either from CVS, or directly. I get the JVM alert box the minute I type a character in a text field, so I cannot either give the name of a cvs server, or even provide a name for a project. I tried to put the USP10.DLL in the Eclipse startup directory as suggested, but it only made things worse (not everytime): Eclipse crashed directly at startup (!).

Comment 53 Guy Melançon 2007-01-09 12:41:51 EST

(In reply to comment #52)

I guess the discussion linking the JVM cras to the USP10.DLL (and thus to Win XP SP2) mislead me ... and I only had the idea to downgrade to JVM 1.5 this morning.

Downgrading the JVM repared the problem for me, which makes it clear that the problem does not link to a bug on Eclipse's side.

Comment 54 Irchad 2007-02-28 12:43:14 EST

Hi all,
I have the same problem when launching eclipse in debug mode when i allocated 1024M of memory, but problem seems to be resolved when i allocated 512M.
I have about 2G of RAM

When launching in normal mode it is ok for both.

Cheers,

IA

Comment 55 Steve Northover 2007-02-28 15:04:40 EST

Felipe, 

This bug report is very confused, but judging from the number of duplicates and the fact that machines are crashing, we need to get to the bottom of it.  Some claim we are passing a bogus "*psc".  Others say that downgrading to JVM 1.5 fixes it.  Are people seeing the same crash?

Can ANYONE who is crashing answer Felipe's question "what font are you using?"  If we can't make it crash here, then we CANT fix it.

Right?

Comment 56 Felipe Heidrich 2007-05-07 17:01:54 EDT

Since nobody answered the question in comment #55 I'll assume that no one is still crashing.

Please reopen this problem report if you still experience this problem - don't forget to say what font you are using, your OS, your VM, version of anything else that you think it can help. Thanks.

closing.

Comment 57 contactkannan 2007-05-29 10:21:41 EDT

Guys

This issue is still happening. I just finished installing XP SP2 and restarted the computer. When I open any file in Eclipse 3.0 and scroll through, it just crashes with the same message:

"An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x74DA5F52
Function=ScriptApplyDigitSubstitution+0x12D0
Library=C:\WINDOWS\system32\USP10.dll

Current Java thread:
	at org.eclipse.swt.internal.win32.OS.ScriptTextOut(Native Method)....."

There should be some fix for this issue. Please someone share your thoughts in this issue.

Felipe Heidrich: I dont know what Font does Eclipse 3.0 uses. I dont know where to find the fonts used by Eclipse.

I would like to reopen this issue please.
Thanks.

Comment 58 Michael Giroux 2007-05-29 10:26:51 EDT

(In reply to comment #57)
> When I open any file in Eclipse 3.0 ...

I have not seen this problem since upgrading to Eclipse 3.2.  Have you tried with a current version of Eclipse?

Comment 59 Felipe Heidrich 2007-05-29 12:49:56 EDT

You can check the font in the preference dialog under General->Appearance->Colors and Fonts.

I never could reproduce this problem. Some people fix it by replacing the usp10.dll, other changing the VM, others changing the size of the heap in the VM, others by getting a new version of Eclipse. 
Please let me know what fix works for you.

Since I don't have a reproducible case, there is nothing I can look at for 3.3.

Comment 60 contactkannan 2007-05-30 08:55:58 EDT

Felipe Heidrich

Please find the details you asked for:
1. Eclipse version 3.0
2. Operation System: Windows XP SP2
3. Fonts Used:
   There are many categories under Colors and Fonts section:
   1. Category > Uncategoried
        > Banner Font - Default (Tahoma-bold-8)
        > Console Text Font - Currently mapped to Text Font (Courier New- regular-10)
        > Text Font - Currently set to the default value (Courier New-regular-10)
        > Java Editor Text Font - Currently mapped to Text Font (Courier New-regular-10)
        > Header Font - Currently set to the default value (Tahoma-bold-12)
   2. Category > Text Compare Appearance
   	> Compare Text Font - Currently mapped to Text Font (Courier New-regular-10)
   	> Java Compare Text Font - Currently mapped to Java Editor Text Font (Courier New-regular-10)
   	
   There are many categories like this, If you could let me know which category you want, I can get the
   information.
   
I haven't tried the new version, I would try but I am not sure whether it  will fix or not.
Please share your thoughts.
 
Thanks.

Comment 61 Carolyn MacLeod 2007-05-31 01:40:14 EDT

Re comment 60,
Please try this experiment:
1) download eclipse 3.2.2 from: 
http://download.eclipse.org/eclipse/downloads/drops/R-3.2.2-200702121330/download.php?dropFile=eclipse-SDK-3.2.2-win32.zip
2) unzip to a new directory (i.e. don't overwrite your eclipse 3.0)
3) startup this new eclipse by double-clicking its eclipse.exe
4) use a new workspace (i.e. don't try to open your current workspace)
5) create a new test java project
6) create a new test java class and paste in some content
7) try to crash

If this does not crash for you, then:

8) try importing projects from your old workspace into this new workspace
   (File->Import... Existing Projects Into Workspace)
9) try to crash again.

If you still cannot crash in this new world, then you might want to just continue to work there.

Comment 62 contactkannan 2007-05-31 04:27:21 EDT

Carolyn MacLeod

Thanks for your suggestion. It Works. Eclipse 3.2.2 on XP SP2 works without any crash.

Thanks everyone for your help.
Cheers.

Comment 63 Carolyn MacLeod 2007-05-31 04:34:09 EDT

You're welcome. Glad to help.

Leaving bug resolution as "won't fix".