Inspiring

Question

Removing compiler problem markers

Forum|Forum|19 years ago
August 29, 2006
17 replies
15479 views

Does anybody know why I keep getting a pop up window that is telling me it can't find a marker id at some location number? I am getting one of these messages about every other time I save and compile and it is getting RATHER ANNOYING!!! What does it mean and how do I eliminate it???

Thanks in advance for helping me lower my blood pressure!!! :)

Have an Ordinary Day...
KomputerMan ~|:-)

This topic has been closed for replies.

E

Elrinth

Participant

I just stumbled upon this error when I had written some faulty xml, then commented it out.

Specifically:

private function MyFuncSetEditorSettings(param0:Object, caller:ComponentEditor, options:Object):void

{

if (Configuration.configuration["componenteditor/undotooltip"])

caller.setStyle("undotooltip", Configuration.configuration["componenteditor/undotooltip"]);

var menu:String = '';/*

menu += '<menu>';

menu += ' <menu label="Use" default="contextmenu"/>';

menu += ' <menu type="separator"/>';

menu += ' <component name="showversions" id="_showversions_" label="Show all versions">';

menu += ' <option id="menupopup" name="menupopup">';

menu += ' <![CDATA[<menu><component name="comparetopreviousversion" id="_comparetopreviousversion_" label="Compare to previous version" /></menu>]]>';

menu += ' </option>';

menu += ' </component>';

menu += ' <component name="comparetopreviousversion" id="_comparetopreviousversion_" label="Compare to previous version"/>';

menu += '</menu>';*/

caller.setStyle("menupopup", menu);

}

It seems the CDATA part was breaking Flash Builder insanely giving the Removing compiler problem markers.

The solution was to remove the CDATA-part and in order to get the error messages go away in Flash Builder 4.6 and 4.7. You had to click Problems tab in bottom, then on the I (other problems) you simply right click and delete the problems

Then it should be working.

Gopinath Ravichandran

Participant

Hi,

I too facing this same problem but I dont know why this issue occur, removing .marker also wont help. I have fixed by deleting the project and re-import it into flash builder.

That worked for me in Flash Builder 4.7

D

detailed_maker15B9

Participant

We have to remove .marker file from all projects inside, in particular main project and its dependent library projects , make sure you close your Eclipse IDE and do , as it will recreate at the time of closing

That worked for me in Flash Builder 4.7

-------- Adobe Flash Builder 4.7\.metadata\.plugins\org.eclipse.core.resources\.projects\<every Project>

M

Michael Peters

Inspiring

Can you believe that this is still present in Flash Builder 4.6. Seems like bug fixing is not part of Adobe's release process as I see the same bugs mentioned in these forums again and again over years and years. I am quite convinced that Adobe doesn't ever look at these forums.

L

Lord_Habicht

Participant

Only thing hat fixed it for me was creating a new workspace and reimport the projects there.

S

Snaux

Participant

http://www.actionscript.org/forums/showthread.php3?p=1088299#post1088299

JabbyPandaUA

Inspiring

Phew, sorry I was mistaken, clearing the file .markers at the location I had mentioned above had fixed the error Removing compiler problem markers".

Flex 3 Beta 1 can wait for now.

A

Anonymous

Hey;

I had the same problem caused by attempting to install flex builder 3 plugin on the Gallileo release of Eclipse. Reverting back to Ganymede the problem persisted in the workspace. It was also very annoying 'cause my current workspace has about 16 projects the majority of which had this issue. I've succesfully got things back up and running and subversion behalving properly and up to date. I used the method decribed above and renamed the .marker files in all of the affected projects. I'm concerned though about the ramifications of doing this.

Does anyone know clearly what purpose(s) these .marker files serve, or can someone point me to the documentation that would explain?

Thanks

-Simon

E

emurmur

Participant

I also got this problem by using Flex Builder 3.2 in Eclipse Gallileo (3.5.1). Going back to Eclipse 3.4.2 and reinstalling Flex Builder did _not_ fix the problem. Deleting the .marker files in the .metadata folder of the workspace (as described by another poster) was the only way I could fix it. Presumably, creating a new workspace and getting from source control again would also fix it because the new workspace would not have .marker files yet.

JabbyPandaUA

Inspiring

I am on Flex Builder 2.0.1 Eclipse plugin (2.0.155577 version) and I am also victim to this problem.

I had located file .markers at slightly different location:
c:\<My workspace dir> >\.metadata\.plugins\org.eclipse.core.resources\.projects\<My project>\.markers

Erasing this file does nothing.. It is recreated again with a new compilation and this vicious error "Removing compiler problem markers" still remains.

I guess, I am ready to move to Flex 3 Beta 1 now =)

M

mike_morearty

Participating Frequently

hawkfanxity, did you try the workaround mentioned by Wigg above? "I fixed this by closing FB2, renaming the file C:\Documents and Settings\<My Username>\My Documents\Flex Builder 2\.metadata\.plugins\org.eclipse.core.resources\.projects\<My Project>\.markes so it wouldn't find it and restarting FB2.

"It may also delete your bookmarks and breakpoints."

The bug that existed in FB 2.0 and was fixed in FB 2.0.1 was that at certain times, such as when starting a new compile, FB would clear out the old markers, but there was a race condition between two threads, so the thread that was trying to delete the old markers would sometimes fail.

However, if the markers themselves, as stored in .markers, are corrupt, then that's a separate issue. Wigg's workaround would seem to imply that somehow the markers got corrupted. Give it a try.