Bug 331263 - Crashing when auto-complete appears.
Summary: Crashing when auto-complete appears.
Status: REOPENED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Windows 7
: P3 critical with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-26 21:09 EST by lopesc CLA
Modified: 2019-09-06 16:08 EDT (History)
6 users (show)

See Also:


Attachments
Eclipse.ini file (337 bytes, text/plain)
2010-11-26 21:11 EST, lopesc CLA
no flags Details
Error message (63.21 KB, image/png)
2010-11-27 13:50 EST, lopesc CLA
no flags Details
.log 3.7 (93.73 KB, application/octet-stream)
2010-11-30 16:14 EST, lopesc CLA
no flags Details
Error 3.7 (77.87 KB, image/png)
2010-11-30 16:17 EST, lopesc CLA
no flags Details
JVM Error Log. (21.63 KB, application/octet-stream)
2010-12-01 14:06 EST, lopesc CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description lopesc CLA 2010-11-26 21:09:44 EST
Build Identifier: M20100909-0800

**NOTE : I HAVE NOT SEEN THIS BUG REPORTED UNDER WINDOWS 7 BEFORE **

Every time I open eclipse this is happening. I am using the latest 64bit JDK 1.6.0_22. Both Eclipse and OS are 64bit. From reading other bug reports with the same problem, I understand that this should have been fixed by now. Why is this happening I've spent far too long looking for answers online at this stage - all the suppoort seems to be for linux.

Reproducible: Always

Steps to Reproduce:
1. Open Eclipse
2. Do something to prompt content assist.
3.
Comment 1 lopesc CLA 2010-11-26 21:11:45 EST
Created attachment 183970 [details]
Eclipse.ini file
Comment 2 lopesc CLA 2010-11-26 21:13:03 EST
Forgot to mention that I have tried re-installing eclipse in case it was one of the plugins.
Comment 3 Remy Suen CLA 2010-11-26 21:19:20 EST
Comment on attachment 183970 [details]
Eclipse.ini file

If Eclipse is crashing, you should look for crash logs. They're probably wherever your Eclipse is installed or possibly where your Eclipse shortcut is (if you use shortcuts).
Comment 4 lopesc CLA 2010-11-26 21:20:15 EST
I checked! There is none.
Comment 5 lopesc CLA 2010-11-26 21:22:21 EST
I checked! There is none.
Comment 6 Stephan Herrmann CLA 2010-11-27 08:16:09 EST
From the information you provided there is no obvious hint at any possible
cause for the crash. So for others to be able to help you, you should try
hard to provide additional information, like errors logged in .metadata/.log
inside your workspace directory, or try different JDKs etc.pp.

If there is indeed a similarity to bug 297279 and thus to its 'master'
bug 283503 the exact version of your operating system and its libraries
might be relevant.

If by crashing you say Eclipse terminates abruptly this indicates an error
within native code (library, OS or JVM). The JDT/Core has no native code
so maybe the folks at SWT can ask you better questions.
Comment 7 lopesc CLA 2010-11-27 13:50:10 EST
Created attachment 183979 [details]
Error message

This is the error message I get each time it crashes.
Comment 8 lopesc CLA 2010-11-27 13:54:35 EST
Here is the log in that appears in .metadata each time it crashes:

SESSION 2010-11-27 18:52:28.051 -----------------------------------------------
eclipse.buildId=M20100909-0800
java.version=1.6.0_22
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_IE
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -clean

!ENTRY org.eclipse.team.core 4 0 2010-11-27 18:52:34.629
!MESSAGE Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project Calculater.
!STACK 1
org.eclipse.team.core.TeamException: Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project Calculater.
	at org.eclipse.team.core.RepositoryProvider.mapNewProvider(RepositoryProvider.java:165)
	at org.eclipse.team.core.RepositoryProvider.mapExistingProvider(RepositoryProvider.java:235)
	at org.eclipse.team.core.RepositoryProvider.getProvider(RepositoryProvider.java:507)
	at org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.isMappedToCVS(CVSLightweightDecorator.java:192)
	at org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.decorate(CVSLightweightDecorator.java:147)
	at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:263)
	at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365)
	at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347)
	at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371)
	at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
!SUBENTRY 1 org.eclipse.team.core 4 0 2010-11-27 18:52:34.630
!MESSAGE Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project Calculater.

!ENTRY org.eclipse.team.core 4 0 2010-11-27 18:52:34.645
!MESSAGE Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project Test.
!STACK 1
org.eclipse.team.core.TeamException: Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project Test.
	at org.eclipse.team.core.RepositoryProvider.mapNewProvider(RepositoryProvider.java:165)
	at org.eclipse.team.core.RepositoryProvider.mapExistingProvider(RepositoryProvider.java:235)
	at org.eclipse.team.core.RepositoryProvider.getProvider(RepositoryProvider.java:507)
	at org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.isMappedToCVS(CVSLightweightDecorator.java:192)
	at org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.decorate(CVSLightweightDecorator.java:147)
	at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:263)
	at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365)
	at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347)
	at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371)
	at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
!SUBENTRY 1 org.eclipse.team.core 4 0 2010-11-27 18:52:34.645
!MESSAGE Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project Test.
Comment 9 lopesc CLA 2010-11-27 13:56:09 EST
(In reply to comment #8)
> Here is the log in that appears in .metadata each time it crashes:
> 
> SESSION 2010-11-27 18:52:28.051 -----------------------------------------------
> eclipse.buildId=M20100909-0800
> java.version=1.6.0_22
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_IE
> Command-line arguments:  -os win32 -ws win32 -arch x86_64 -clean
> 
> !ENTRY org.eclipse.team.core 4 0 2010-11-27 18:52:34.629
> !MESSAGE Could not instantiate provider
> org.tigris.subversion.subclipse.core.svnnature for project Calculater.
> !STACK 1
> org.eclipse.team.core.TeamException: Could not instantiate provider
> org.tigris.subversion.subclipse.core.svnnature for project Calculater.
>     at
> org.eclipse.team.core.RepositoryProvider.mapNewProvider(RepositoryProvider.java:165)
>     at
> org.eclipse.team.core.RepositoryProvider.mapExistingProvider(RepositoryProvider.java:235)
>     at
> org.eclipse.team.core.RepositoryProvider.getProvider(RepositoryProvider.java:507)
>     at
> org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.isMappedToCVS(CVSLightweightDecorator.java:192)
>     at
> org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.decorate(CVSLightweightDecorator.java:147)
>     at
> org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:263)
>     at
> org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81)
>     at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>     at
> org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365)
>     at
> org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347)
>     at
> org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371)
>     at
> org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331)
>     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !SUBENTRY 1 org.eclipse.team.core 4 0 2010-11-27 18:52:34.630
> !MESSAGE Could not instantiate provider
> org.tigris.subversion.subclipse.core.svnnature for project Calculater.
> 
> !ENTRY org.eclipse.team.core 4 0 2010-11-27 18:52:34.645
> !MESSAGE Could not instantiate provider
> org.tigris.subversion.subclipse.core.svnnature for project Test.
> !STACK 1
> org.eclipse.team.core.TeamException: Could not instantiate provider
> org.tigris.subversion.subclipse.core.svnnature for project Test.
>     at
> org.eclipse.team.core.RepositoryProvider.mapNewProvider(RepositoryProvider.java:165)
>     at
> org.eclipse.team.core.RepositoryProvider.mapExistingProvider(RepositoryProvider.java:235)
>     at
> org.eclipse.team.core.RepositoryProvider.getProvider(RepositoryProvider.java:507)
>     at
> org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.isMappedToCVS(CVSLightweightDecorator.java:192)
>     at
> org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.decorate(CVSLightweightDecorator.java:147)
>     at
> org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:263)
>     at
> org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81)
>     at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>     at
> org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365)
>     at
> org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347)
>     at
> org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371)
>     at
> org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331)
>     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !SUBENTRY 1 org.eclipse.team.core 4 0 2010-11-27 18:52:34.645
> !MESSAGE Could not instantiate provider
> org.tigris.subversion.subclipse.core.svnnature for project Test.

I know alot of the above has to do with the subclipse plugin that I had installed before I rein-stalled eclipse to see if it were a dodgy plugin causing the problem.
Comment 10 Felipe Heidrich CLA 2010-11-29 09:44:33 EST
I don't have enough information to work on this problem.

Please try to find the native crash log (the one that is created by the VM when it crashes). It should be on the same folder where the VM was launched (usually the same folder where you double-clicked eclipse.exe but not necessarily if you used a shortcut or the command prompt).

Does the problem happen without the subversion plugin ? If does, what do you get in the .log ?

Does the problem happen with a new Eclipse (e.g Eclipse 3.7 M3) ?
Comment 11 lopesc CLA 2010-11-29 10:03:26 EST
(In reply to comment #10)

> Please try to find the native crash log (the one that is created by the VM when
> it crashes). It should be on the same folder where the VM was launched (usually
> the same folder where you double-clicked eclipse.exe but not necessarily if you
> used a shortcut or the command prompt).

I have looked in the Eclipse folder, it's not there.
Could you give me the name of it so I could search for it.

> Does the problem happen without the subversion plugin ? If does, what do you
> get in the .log ?

Yes. That is the log attached - a reinstall of 3.6.1 without installing subclipse

> Does the problem happen with a new Eclipse (e.g Eclipse 3.7 M3) ?
Haven't tried. Is that a new beta? From what I've read this problem was should have been fixed by 3.6.
Comment 12 Felipe Heidrich CLA 2010-11-29 10:22:03 EST
GTK

Remove the javadoc you added (only windows needs javadoc; we have tooling that copies the javadoc of windows to all others platforms).

ExpandBar#setOrientatio(boolean) needs to call setOrientation on the ExpandItems (just like you did for TabFolder).


Menu#setOrientatio(boolean) needs to call setOrientation on the MenuItems (just like you did for TabFolder).
(I suspect) MenuItem#setOrientatio(boolean) needs to call setOrientation on the 'menu' (for CASCADE menu items). See MenuItem#reskinChildren() as an example.

Scrollable#setOrientatio(boolean) needs to call setOrientation on the ScrollBars (see Scrollable#reskinChildren(int) for example how to propagate a change from the Scrollable down to the ScrollBars).

Table#setOrientatio(boolean) needs to call setOrientation on the TableColumns. Same thing you did for the TableItems you need to do for the TableColumns. (see Table#reskinChildren())

Tree#setOrientatio(boolean) needs to call setOrientation on the TreeColumns. Same thing you did for the TreeItems you need to do for the TreeColumns. (see Tree#reskinChildren())

In Composite#setOrientatio(boolean) instead of:

void setOrientation (boolean create) { 
	super.setOrientation (create); 
	if (!create) { 
		int dir = (style & SWT.RIGHT_TO_LEFT) != 0 ? OS.GTK_TEXT_DIR_RTL : 
			OS.GTK_TEXT_DIR_LTR; 
		Control [] list = _getChildren (); 
		for (int i=0; i<list.length; i++) { 
			list[i].setOrientation ((dir == OS.GTK_TEXT_DIR_RTL) ? SWT.RIGHT_TO_LEFT : SWT.LEFT_TO_RIGHT); 
		} 
	} 
} 

What about this:
void setOrientation (boolean create) { 
	super.setOrientation (create); 
	if (!create) { 
		int flags = SWT.RIGHT_TO_LEFT | SWT.LEFT_TO_RIGHT;
		int orientation = style & flags;
		Control [] list = _getChildren (); 
		for (int i=0; i<list.length; i++) { 
			list[i].setOrientation (orientation); 
		} 
	} 
}
Comment 13 Felipe Heidrich CLA 2010-11-29 10:23:25 EST
Please ignore my last comment, it was meant to another bug and accidently paste in here. Sorry for the confusion.
Comment 14 Felipe Heidrich CLA 2010-11-29 10:41:39 EST
(In reply to comment #11)
> (In reply to comment #10)
> Could you give me the name of it so I could search for it.

Depends on the VM, but try:
hs_err_pid*.log 
javacore*

> > Does the problem happen without the subversion plugin ? If does, what do you
> > get in the .log ?
> Yes. That is the log attached - a reinstall of 3.6.1 without installing
> subclipse
Funny, I still see subversion packages in the stack frame.


> > Does the problem happen with a new Eclipse (e.g Eclipse 3.7 M3) ?
> Haven't tried. Is that a new beta? From what I've read this problem was should
> have been fixed by 3.6.

Yes, could you download it and make sure it is indeed fixed ?
Thank you
Comment 15 lopesc CLA 2010-11-29 11:26:05 EST
(In reply to comment #14)
> (In reply to comment #11)
> > (In reply to comment #10)
> > Could you give me the name of it so I could search for it.
> 
> Depends on the VM, but try:
> hs_err_pid*.log 
> javacore*
> 
> > > Does the problem happen without the subversion plugin ? If does, what do you
> > > get in the .log ?
> > Yes. That is the log attached - a reinstall of 3.6.1 without installing
> > subclipse
> Funny, I still see subversion packages in the stack frame.
> 
> 
> > > Does the problem happen with a new Eclipse (e.g Eclipse 3.7 M3) ?
> > Haven't tried. Is that a new beta? From what I've read this problem was should
> > have been fixed by 3.6.
> 
> Yes, could you download it and make sure it is indeed fixed ?
> Thank you

3.7? Is there a link?
Comment 16 Felipe Heidrich CLA 2010-11-30 10:08:49 EST
(In reply to comment #15)
> 3.7? Is there a link?

http://download.eclipse.org/eclipse/downloads/
Comment 17 lopesc CLA 2010-11-30 16:13:03 EST
(In reply to comment #16)
> (In reply to comment #15)
> > 3.7? Is there a link?
> 
> http://download.eclipse.org/eclipse/downloads/

Ok so here's what I've just done. 
Downloaded 3.7 M3. Made a new workspace. 
Created a new project. 
Began writing a class. As soon as content assist opened, eclipse exited.
I will attach the error message as "Error 3.7" though i think it's the same as the previous one. I have aslo attached the .log file from .metadata folder inn the workspace (attached as ".log 3.7").
There is NO error log in the eclipse installation folder.

Anything else I can do?
Comment 18 lopesc CLA 2010-11-30 16:14:31 EST
Created attachment 184186 [details]
.log 3.7
Comment 19 lopesc CLA 2010-11-30 16:17:14 EST
Created attachment 184187 [details]
Error 3.7
Comment 20 Dani Megert CLA 2010-12-01 02:27:56 EST
The log has lots of entries which indicates that it's not a clean install with new workspace. Are you sure that this is the .log from the new workspace?

>Anything else I can do?
Try again to find the VM crash log - look in:
- the eclipse.exe location
- the current directory where you called/started eclipse
- C:\Windows\system32

Also, do you use a 64-bit JRE? I'm asking because you run the 64 bit Eclipse build. See also:
http://www.oracle.com/technetwork/java/javase/system-configurations-139801.html
Comment 21 lopesc CLA 2010-12-01 10:45:30 EST
(In reply to comment #20)
> The log has lots of entries which indicates that it's not a clean install with
> new workspace. Are you sure that this is the .log from the new workspace?
Absolutely! Look at the heading of the .log - " !SESSION 2010-11-30 21:00:05.400. " Last night (I am in GMT timezone by the way, 5/6 hours ahead of you I think).

> >Anything else I can do?
> Try again to find the VM crash log - look in:
> - the eclipse.exe location
> - the current directory where you called/started eclipse
> - C:\Windows\system32
I've said twice already that's it' not there. Is there any way I can force a crash log?

> Also, do you use a 64-bit JRE? I'm asking because you run the 64 bit Eclipse
> build. See also:
> http://www.oracle.com/technetwork/java/javase/system-configurations-139801.html

Again, I have stated already that I am using 64 bit JDK 1.6.)_22
Comment 22 Dani Megert CLA 2010-12-01 10:48:26 EST
(In reply to comment #21)
> (In reply to comment #20)
> > The log has lots of entries which indicates that it's not a clean install with
> > new workspace. Are you sure that this is the .log from the new workspace?
> Absolutely! Look at the heading of the .log - " !SESSION 2010-11-30
> 21:00:05.400. " Last night (I am in GMT timezone by the way, 5/6 hours ahead of
> you I think).
OK, so let's start off there. Which package/download did you use exactly from
http://download.eclipse.org/eclipse/downloads/
?
Comment 23 lopesc CLA 2010-12-01 11:04:27 EST
(In reply to comment #22)
> (In reply to comment #21)
> > (In reply to comment #20)
> > > The log has lots of entries which indicates that it's not a clean install with
> > > new workspace. Are you sure that this is the .log from the new workspace?
> > Absolutely! Look at the heading of the .log - " !SESSION 2010-11-30
> > 21:00:05.400. " Last night (I am in GMT timezone by the way, 5/6 hours ahead of
> > you I think).
> OK, so let's start off there. Which package/download did you use exactly from
> http://download.eclipse.org/eclipse/downloads/
> ?

It was in fact this one http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/indigo/M3/eclipse-java-indigo-M3-win32-x86_64.zip
Comment 24 Markus Keller CLA 2010-12-01 13:01:48 EST
(In reply to comment #23)
> http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/indigo/M3/eclipse-java-indigo-M3-win32-x86_64.zip

I cannot reproduce any problems with this build, JDK6_22 64bit, and a brand new workspace. The .log is empty right after startup and also when I create a Java project and a class, and then use content assist.


(In reply to comment #19)
> Created an attachment (id=184187) [details]
> Error 3.7

Looks like you forgot to set an explicit VM here (it's using the default Windows VM). I also see more arguments like -Dosgi.requiredJavaVersion=1.5


(In reply to comment #17)
OK, if the log from comment 18 is really from a fresh workspace, then the log entries look like a p2 problem:

!ENTRY org.eclipse.equinox.preferences 4 4 2010-11-30 21:00:27.528
!MESSAGE Exception saving preferences to: C:/Users/Cristover/.eclipse/org.eclipse.platform_3.7.0_920333535/p2/org.eclipse.equinox.p2.engine/profileRegistry/epp.package.java.profile/.data/.settings/org.eclipse.equinox.p2.metadata.repository.prefs.
!STACK 0
java.io.FileNotFoundException: C:\Users\Cristover\.eclipse\org.eclipse.platform_3.7.0_920333535\p2\org.eclipse.equinox.p2.engine\profileRegistry\epp.package.java.profile\.data\.settings\org.eclipse.equinox.p2.metadata.repository.prefs (The requested operation cannot be performed on a file with a user-mapped section open)
	at java.io.FileOutputStream.open(Native Method)


How exactly do you start Eclipse (command line including arguments)?
Comment 25 lopesc CLA 2010-12-01 14:05:38 EST
Start using Start menu shortcut.(In reply to comment #24)
> (In reply to comment #23)
> > http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/indigo/M3/eclipse-java-indigo-M3-win32-x86_64.zip
> 
> I cannot reproduce any problems with this build, JDK6_22 64bit, and a brand new
> workspace. The .log is empty right after startup and also when I create a Java
> project and a class, and then use content assist.
> 
> 
> (In reply to comment #19)
> > Created an attachment (id=184187) [details] [details]
> > Error 3.7
> 
> Looks like you forgot to set an explicit VM here (it's using the default
> Windows VM). I also see more arguments like -Dosgi.requiredJavaVersion=1.5
> 
> 
> (In reply to comment #17)
> OK, if the log from comment 18 is really from a fresh workspace, then the log
> entries look like a p2 problem:
> 
> !ENTRY org.eclipse.equinox.preferences 4 4 2010-11-30 21:00:27.528
> !MESSAGE Exception saving preferences to:
> C:/Users/Cristover/.eclipse/org.eclipse.platform_3.7.0_920333535/p2/org.eclipse.equinox.p2.engine/profileRegistry/epp.package.java.profile/.data/.settings/org.eclipse.equinox.p2.metadata.repository.prefs.
> !STACK 0
> java.io.FileNotFoundException:
> C:\Users\Cristover\.eclipse\org.eclipse.platform_3.7.0_920333535\p2\org.eclipse.equinox.p2.engine\profileRegistry\epp.package.java.profile\.data\.settings\org.eclipse.equinox.p2.metadata.repository.prefs
> (The requested operation cannot be performed on a file with a user-mapped
> section open)
>     at java.io.FileOutputStream.open(Native Method)
> 
> 
> How exactly do you start Eclipse (command line including arguments)?

Start menu shortcut, no arguments. Added  -XX:ErrorFile argument to the eclipse.ini file and hurrah! We have an error log file! Hopefully this helps somewhat.
Comment 26 lopesc CLA 2010-12-01 14:06:27 EST
Created attachment 184288 [details]
JVM Error Log.
Comment 27 Dani Megert CLA 2010-12-02 02:04:44 EST
Looks like a bug in an IE library. I suggest to update to the latest version.

Most likely a duplicate of bug 279680.
Comment 28 lopesc CLA 2010-12-02 05:48:35 EST
(In reply to comment #27)
> Looks like a bug in an IE library. I suggest to update to the latest version.
> 
> Most likely a duplicate of bug 279680.

Of IE? I don't use IE.
Comment 29 lopesc CLA 2010-12-02 05:50:30 EST
(In reply to comment #28)


>  Most likely a duplicate of bug 279680.

Also, that bug isn't resolved.
Comment 30 Dani Megert CLA 2010-12-02 05:52:21 EST
> Also, that bug isn't resolved.
Who said that?

>Of IE? I don't use IE.
No, but Eclipse does if it's not configured otherwise.
Comment 31 lopesc CLA 2010-12-02 06:02:06 EST
(In reply to comment #30)
> > Also, that bug isn't resolved.
> Who said that?
> 
> >Of IE? I don't use IE.
> No, but Eclipse does if it's not configured otherwise.

So tell me if I've configured it correctly yo use firefox.
I've done the following: Window > Preferences > General > Web Browser > Search. Located the Firefox directory, at which point Firefox appeared in the web browser box. Selected this, yet eclipse still crashes.
Comment 32 Dani Megert CLA 2010-12-02 07:07:47 EST
(In reply to comment #31)
> (In reply to comment #30)
> > > Also, that bug isn't resolved.
> > Who said that?
> > 
> > >Of IE? I don't use IE.
> > No, but Eclipse does if it's not configured otherwise.
> 
> So tell me if I've configured it correctly yo use firefox.
> I've done the following: Window > Preferences > General > Web Browser > Search.
> Located the Firefox directory, at which point Firefox appeared in the web
> browser box. Selected this, yet eclipse still crashes.
Right. This only sets the Web browser but not what's used by the SWT Browser widget.
Comment 33 lopesc CLA 2010-12-02 09:15:21 EST
(In reply to comment #32)
> (In reply to comment #31)
> > (In reply to comment #30)
> > > > Also, that bug isn't resolved.
> > > Who said that?
> > > 
> > > >Of IE? I don't use IE.
> > > No, but Eclipse does if it's not configured otherwise.
> > 
> > So tell me if I've configured it correctly yo use firefox.
> > I've done the following: Window > Preferences > General > Web Browser > Search.
> > Located the Firefox directory, at which point Firefox appeared in the web
> > browser box. Selected this, yet eclipse still crashes.
> Right. This only sets the Web browser but not what's used by the SWT Browser
> widget.

How do i do this?
Comment 34 Felipe Heidrich CLA 2010-12-02 10:00:52 EST
I agree with Dani (duplicate of 279680).

Adding Grant to CC list, maybe he knows a way to make the Browser control to always use FF (as a workaround).

*** This bug has been marked as a duplicate of bug 279680 ***
Comment 35 Grant Gayed CLA 2010-12-02 10:38:03 EST
A Browser created with style SWT.NONE, which is the case here, will not use mozilla as the underlying renderer on platforms other than *ix.
Comment 36 lopesc CLA 2010-12-02 11:27:49 EST
(In reply to comment #35)
> A Browser created with style SWT.NONE, which is the case here, will not use
> mozilla as the underlying renderer on platforms other than *ix.

Well it doesn't even have to be Firefox, I am just looking for a solution to the problem. I don't understand how eclipse goes from working fine to crashing. The only thing that ever changes is the JDK with new updates and the issue is happening with both 3.6.1 and 3.7 - which(In reply to comment #35)
> A Browser created with style SWT.NONE, which is the case here, will not use
> mozilla as the underlying renderer on platforms other than *ix.

So how do I solve the problem?
Comment 37 Felipe Heidrich CLA 2010-12-02 12:02:45 EST
(In reply to comment #36)
> So how do I solve the problem?

I just read bug 279680 and it seems this is not a SWT bug, it is possible that we can not do anything to help (as far as changing SWT code goes). Sorry.

Can you go back using your old JDK as a workaround ?
Comment 38 lopesc CLA 2010-12-02 12:40:28 EST
(In reply to comment #37)
> (In reply to comment #36)
> > So how do I solve the problem?
> 
> I just read bug 279680 and it seems this is not a SWT bug, it is possible that
> we can not do anything to help (as far as changing SWT code goes). Sorry.
> 
> Can you go back using your old JDK as a workaround ?

Look: https://bugs.eclipse.org/bugs/show_bug.cgi?id=283503 . That bug is the exact same one as this. It was said that it would be fixed by 3.6 yet I am still having the same problem. If the JDK alone were the issue, then many others would have this problem. It is not affecting anything else on my system
Comment 39 Eclipse Webmaster CLA 2019-09-06 16:08:45 EDT
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.