Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361419 - Pressing F1 crashes Eclipse
Summary: Pressing F1 crashes Eclipse
Status: CLOSED DUPLICATE of bug 353740
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows 7
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: platform-ua-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-19 11:27 EDT by Chris CLA
Modified: 2011-10-19 11:42 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris CLA 2011-10-19 11:27:21 EDT
Build Identifier: 20110916-0149

(64bit)
Whenever I press F1 the help menu appears on the right, then as it's "Indexing help" it gets about half way then the program just closes.
Pressing F1 again before it happens doesn't stop it from crashing, it's like an accidental-touch death button where I have to race against the clock to save my work before it crashes.

Reproducible: Always

Steps to Reproduce:
1. Hit the F1 key
Comment 1 Remy Suen CLA 2011-10-19 11:34:31 EDT
(In reply to comment #0)
> Whenever I press F1 the help menu appears on the right, then as it's "Indexing
> help" it gets about half way then the program just closes.

We need VM crash logs if you can find any.

Are you using Java 7?
Comment 2 Chris CLA 2011-10-19 11:37:55 EDT
(In reply to comment #1)
> (In reply to comment #0)
> > Whenever I press F1 the help menu appears on the right, then as it's "Indexing
> > help" it gets about half way then the program just closes.
> 
> We need VM crash logs if you can find any.
> 
> Are you using Java 7?

Yes, Java 7
Where can I find the crash logs? (relative newbie)
If you mean the crash pop-up that comes up after Eclipse closes, they've stopped appearing recently after a crash, for some reason.
Comment 3 Remy Suen CLA 2011-10-19 11:42:10 EDT

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