Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344440 - Dead lock in indexer job
Summary: Dead lock in indexer job
Status: CLOSED DUPLICATE of bug 343175
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 8.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Doug Schaefer CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-02 08:17 EDT by Jens Elmenthaler CLA
Modified: 2011-05-03 13:12 EDT (History)
1 user (show)

See Also:


Attachments
stack trace (35.01 KB, text/plain)
2011-05-02 08:20 EDT, Jens Elmenthaler CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Elmenthaler CLA 2011-05-02 08:17:18 EDT
Build Identifier: HEAD

I cannot exactly say which action it triggers. It just happens from time to time that the indexer stops working. The progress view is showing the C/C++ Indexer job all the time.

Reproducible: Sometimes
Comment 1 Jens Elmenthaler CLA 2011-05-02 08:20:33 EDT
Created attachment 194480 [details]
stack trace
Comment 2 Anton Leherbauer CLA 2011-05-02 09:09:49 EDT
I believe this is caused by bug 343948.  I can't see a deadlock in the stack trace, but two threads are operating on the same AST which can cause weird behavior.  Should be fixed if you update to HEAD as of now.
Comment 3 Jens Elmenthaler CLA 2011-05-02 09:24:05 EDT
(In reply to comment #2)
> I believe this is caused by bug 343948.  I can't see a deadlock in the stack
> trace, but two threads are operating on the same AST which can cause weird
> behavior.  Should be fixed if you update to HEAD as of now.
Cool, I'll test it.
Comment 4 Markus Schorn CLA 2011-05-03 12:31:52 EDT
The same infinite loop is reported in bug 343175 comment 6

*** This bug has been marked as a duplicate of bug 343175 ***
Comment 5 Jens Elmenthaler CLA 2011-05-03 13:12:00 EDT
(In reply to comment #4)
> The same infinite loop is reported in bug 343175 comment 6
> *** This bug has been marked as a duplicate of bug 343175 ***
Confirmed. After updating from yesterday's HEAD I don't see that problem any longer.