Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336966 - [markers] Better scheduling of the delete and update AJ markers job
Summary: [markers] Better scheduling of the delete and update AJ markers job
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: Core (show other bugs)
Version: 2.1.2   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: 2.1.3   Edit
Assignee: AJDT-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-11 11:40 EST by Andrew Eisenberg CLA
Modified: 2011-04-15 12:12 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 Andrew Eisenberg CLA 2011-02-11 11:40:44 EST 
When the DeleteAndUpateAJMarkers job is running in the background, it is possible to get UI lockup if a user tries to save a file that is part of the job.

We should be more careful about which locks we are grabbing and be better about releasing them sooner.

Currently, DeleteAndUpateAJMarkers first deletes all old markers and then adds the new ones.  Instead, we should be able to delete all markers for a single file, and then run the updates for that single file.  And we continue to do this for all files individually.  In this case, we would only need to grab a lock on a single file at a time.
Comment 1 Andrew Eisenberg CLA 2011-02-18 12:30:15 EST 
I have made a few small changes that I think will help in this area.  I won't close this issue until I am more certain of this, though.
Comment 2 Andrew Eisenberg CLA 2011-04-15 12:12:31 EDT 
I think this is ready to be closed as fixed.