Bug 495058 - Indexing job manager is not awaken immediately after receiving new requests
Summary: Indexing job manager is not awaken immediately after receiving new requests
Status: NEW
Alias: None
Product: DLTK
Classification: Technology
Component: Common (show other bugs)
Version: 5.5   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: dltk.common-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-31 14:34 EDT by Bartlomiej Laczkowski CLA
Modified: 2016-06-01 00:00 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bartlomiej Laczkowski CLA 2016-05-31 14:34:08 EDT 
If indexing job manager (org.eclipse.dltk.internal.core.search.processing.JobManager) goes to idle state it calls delaySignal.wait(500) and if there is some request being passed in the meantime then it won't be executed until this 500 ms time will pass. I think that delaySignal.notify() should be always called whenever some new request is passed to the job queue to awake the indexer thread.
Comment 1 Eclipse Genie CLA 2016-06-01 00:00:08 EDT 
New Gerrit change created: https://git.eclipse.org/r/74099