Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 52477 - [Markers] Clicking on stale marker generates error to log
Summary: [Markers] Clicking on stale marker generates error to log
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Tod Creasey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 71649 77554 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-02-19 10:11 EST by Tod Creasey CLA
Modified: 2005-11-02 15:09 EST (History)
6 users (show)

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 Tod Creasey CLA 2004-02-19 10:11:51 EST 
20040219

If you are rebuilding the workbench and clicking around on the problems view 
if you hit a stale marker you will get an error like 

Error accessing marker type
Reason:
Marker id: 2799 not found.

In your log.
Comment 1 John Arthorne CLA 2004-10-19 10:20:30 EDT 
*** Bug 71649 has been marked as a duplicate of this bug. ***
Comment 2 John Arthorne CLA 2004-10-19 10:27:43 EDT 
The easy fix is to call IMarker.exists() before trying to open the corresponding
editor in ActionOpenMarker. Of course this leaves a small timing window since
the marker could be deleted after calling exists() and before trying to open it,
but it should greatly reduce the number of log error messages here.
Comment 3 DJ Houghton CLA 2004-11-03 09:54:10 EST 
*** Bug 77554 has been marked as a duplicate of this bug. ***
Comment 4 Rafael Chaves CLA 2005-03-15 12:27:54 EST 
This is quite annoying. My scenario is not that unusual. I am using the Problems
view to find broken references to a method that had its name changed
(refactoring was not used). So my work flow is: click on first marker, manually
fix the code (more than one occurrence), save, click the first entry on the
problems view again for the next file (but the first entry is still showing the
old marker). Then the error log view opens (on top of the problems view) to show
the added entries, so I have to switch back to the other view.

This may be seen as a user error. But if I had some kind of clue that the marker
was stale (a beep), I would rather wait until the view refreshed, or try to look
for the first marker for the next file.
Comment 5 Tod Creasey CLA 2005-11-02 15:09:14 EST 
Stale markers are now cleaned out on rebuild