Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332449 - Sometimes Search View is damaged
Summary: Sometimes Search View is damaged
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Search (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Search-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-13 11:02 EST by Kirstin Weber CLA
Modified: 2011-02-01 06:59 EST (History)
3 users (show)

See Also:


Attachments
Screenshot of the Search View (30.75 KB, image/png)
2010-12-13 11:05 EST, Kirstin Weber CLA
no flags Details
Log file (43.37 KB, text/plain)
2011-02-01 04:42 EST, Kirstin Weber CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kirstin Weber CLA 2010-12-13 11:02:34 EST
Build Identifier: I20100608-0911

Sometimes when running a search in the Search View the results are not shown correctly. Only the tree structure and the icons are shown but no text.

When it happended some weeks ago I have closed the Search View, then restarted Eclipse, then rebooted my PC but nothing helped. After creating a new Workspace the Search View worked again.

Today, I had the same problem again but I did nothing for fixing the problem because I had something else to do for some hours. Then I have started a new search and it worked again.


Reproducible: Sometimes

Steps to Reproduce:
Open the Search View and run a search. The problem appears were seldom.
Comment 1 Kirstin Weber CLA 2010-12-13 11:05:31 EST
Created attachment 185074 [details]
Screenshot of the Search View

The screenshot shows the damaged Search View. I used black for hiding product specific information.
Comment 2 Sergey Prigogin CLA 2011-01-31 10:46:28 EST
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?
Comment 3 James Blackburn CLA 2011-01-31 11:01:26 EST
Could you also attach the contents of your workspace log: .metadata/.log?
Comment 4 Kirstin Weber CLA 2011-01-31 11:04:11 EST
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.
Comment 5 Kirstin Weber CLA 2011-01-31 11:20:19 EST
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.
Comment 6 Sergey Prigogin CLA 2011-01-31 12:42:28 EST
File search is not part of CDT.
Comment 7 Dani Megert CLA 2011-02-01 02:28:11 EST
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.
Comment 8 Kirstin Weber CLA 2011-02-01 04:42:34 EST
Created attachment 188032 [details]
Log file

This is the log file from yesterday when the problem occurred.
Comment 9 Dani Megert CLA 2011-02-01 06:48:37 EST
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.
Comment 10 Kirstin Weber CLA 2011-02-01 06:52:29 EST
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?
Comment 11 Dani Megert CLA 2011-02-01 06:59:10 EST
(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.