| Summary: | Sometimes Search View is damaged | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Kirstin Weber <kirstin.weber> | ||||||
| Component: | Search | Assignee: | Platform-Search-Inbox <platform-search-inbox> | ||||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | daniel_megert, eclipse.sprigogin, jamesblackburn+eclipse | ||||||
| Version: | 3.6 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Kirstin Weber
Created attachment 185074 [details]
Screenshot of the Search View
The screenshot shows the damaged Search View. I used black for hiding product specific information.
I've never seen this behavior. In order to make progress on this bug somebody would have to be able to reproduce it. What kind of search were you using, C/C++ or File? Does the problem happen only with that specific searach type? Could you also attach the contents of your workspace log: .metadata/.log? I always use "File Search" so I do not know if there are similar problems with other searches. The last time when I had the problem was in December. Until today the problem did not occur again. But some hours ago I had it again. I restarted the search several times but it kept broken. Now - some hours later - I run the search again and everything is fine. It is really strange. Perhaps it is a memory problem and the garbage collecter have run between the searches. Before I upload the log file I must ask if I am allowed to do it. I will do it tomorrow because the person who might know it is not here today. File search is not part of CDT. It could be a out of handle situation i.e. your OS simply ran out of handles and it was visible in the Search view. As Sergey already pointed out, there's nothing we can do without steps or the log pointing to something being wrong. (In reply to comment #5) > Before I upload the log file I must ask if I am allowed to do it. I will do it > tomorrow because the person who might know it is not here today. You could obscure non-Eclipse packages and types in the .log. Created attachment 188032 [details]
Log file
This is the log file from yesterday when the problem occurred.
The .log doesn't seem to be related to the problem. I really think it's either an out of handle or caused by some other third-party plug-in. Sorry, we can't do anything without more data. An assumption is that maybe the handlers are not closed when a resource is out of sync. Is everything cleaned up correctly during the exceptions that occur when a resource is out of sync? (In reply to comment #10) > An assumption is that maybe the handlers are not closed when a resource is out > of sync. The "resources" are files and not related to UI handles. |