Bugzilla – Full Text Bug Listing
| Summary: | RSE - Editor could not be initialized. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] Target Management | Reporter: | Aaron <kc8iqw> | ||||
| Component: | RSE | Assignee: | dsdp.tm.rse-inbox <tm.rse-inbox> | ||||
| Status: | NEW --- | QA Contact: | Martin Oberhuber <mober.at+eclipse> | ||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | kc8iqw, remy.suen | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 205159 [details]
Initial Java Runtime Error when duplicating the problem
A "work around" to this bug is to close any open files before closing Eclipse, or a project especially if they are a part of an RSE remote project. A work around to the 2nd part of the bug, the "resource X not found" for RSE projects is to close the java run-time error and then close eclipse before establishing the RSE session or attempting to open the file. This will prevent the need to delete the histroy.index file. RSE bugs go to RSE. (In reply to comment #3) > RSE bugs go to RSE. I put it in the UI only because part of it is not RSE specific. The Java Runtime Error will occur if you have a file open in a project, close the project, close eclipse and open it again. The "second part" of the bug, the resource not being found, is RSE specific. (In reply to comment #4) > The Java > Runtime Error will occur if you have a file open in a project, close the > project, close eclipse and open it again. The "second part" of the bug, the > resource not being found, is RSE specific. Not sure I quite understand or see the problem you're describing. If I close a local project, the opened file's editor gets closed. When I restart Eclipse, I have no editors open and no errors. Sorry about that. Appears as the local project portion of my report was a conflict somewhere between a plugin I had and the android tools. I will tinker around some more to see if I can duplicate it again. I am still able to duplicate the RSE part of this bug with a clean install. |
Build Identifier: M20110909-1335 I am using a remote project (Linux host) and if I leave file open when I close Eclipse and re-open I get the error "Could not open the editor: Editor could not be initialized.". See the error details in the attached file "eclipse initial runtime error.txt". This same error can be replicated by "closing" a local project and opening it again with a file open. This is cause because the connection to the server is not yet established. This is part of the bug. The editor should either close the files before exiting, or, establish a connection to the remote system first. What makes this MUCH MUCH more annoying is, after establishing the RSE connections and attempting to open the file, the error "Resource '/{projectname}/{filename}' does not exist." In my case "Resource '/DCCM-Dev_dccm-dev/functions.php' does not exist.". The only way I can find to get rid of this message is to go to the projects .indexes directory under the workspace and delete the history.index file. (My path is workspace\.metadata\.plugins\org.eclipse.core.resources\.projects\DCCM-Dev_dccm-dev\.indexes) I have not experienced the inability to open the file on a local project, but the java runtime error does occur if you have "closed" the project with a file open and then close the IDE. Reproducible: Always Steps to Reproduce: 1. Create a remote project from RSE 2. Open a file in the remote project 3. Close eclipse without closing the project or file. 4. Open eclipse 5. Close the runtime error. 6. Establish the RSE session (say by double-clicking on the project name to open it) and try to open the file that was previously open. ---- Local runtime bug ---- 1. Create a local project 2. Open a file 3. "Close" the project with the file open. 4. Close Eclipse 5. Open Eclipse. 6. --- Note --- The file should open on a local project, but not a remote project even after the RSE session is established.