Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362669 - Invalid thread access from SWT
Summary: Invalid thread access from SWT
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-02 09:31 EDT by Thomas Watson CLA
Modified: 2019-11-14 03:15 EST (History)
1 user (show)

See Also:


Attachments
error log (917.42 KB, text/plain)
2011-11-02 09:31 EDT, Thomas Watson CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Watson CLA 2011-11-02 09:31:54 EDT
Created attachment 206325 [details]
error log

Build I20111027-1910

When eclipse was not running I switched to a branch that did not contain many of my projects that I had in my workspace.  I then launched eclipse and noticed that the latest eGit automatically closes the projects that do not exist.  This is great because before eGit would leave these projects open and dirty my local repo with a bunch of .project files for the projects that did not exist.

This reminded me that I should switch branches back to master.  So I closed Eclipse and switched branches back to master and restarted eclipse to see if eGit would automatically reopen the projects (it did not, but not sure I should expect it to).

When opening my workspace I got lots of SWT errors for Invalid thread access.  See the attached log.  Not sure if these errors are related to the things I described above or some fluke.  Restarting eclipse seemed to correct the issue.  The result was that the editors were non-functional until I restarted.
Comment 1 Remy Suen CLA 2011-11-02 09:36:55 EDT
(In reply to comment #0)
> So I closed
> Eclipse and switched branches back to master and restarted eclipse to see if
> eGit would automatically reopen the projects (it did not, but not sure I should
> expect it to).

You want bug 350866.

> When opening my workspace I got lots of SWT errors for Invalid thread access.

I've seen this problem before. It may or may not be happening more because of Eclipse 4. Also see bug 223381 and bug 296512.
Comment 2 Lars Vogel CLA 2019-11-14 03:15:42 EST
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.