I hit the same bug in FlexBuilder on Friday. I also found the only
way to
fix it was to rebuild the entire project.
One thing I did note was that
it seemed to be caused when I was
messing around with the project bin output.
I had to trouble shoot
some _javascript_ bugs in my wrapper HTML and this
required me to
publish my source to my localhost server. To do this I had to
move my
output folder to a different location. It worked for a bit but then
I
moved the location back (to keep CVS inline) and this is when
everything
blew up. Even saving html files caused Eclipse to throw
this error.
I
will keep my eyes open for possible causes if I hit it again, but
rebuilding
is the way to solve it. Thanks for the tip Mike...
- James
ERROR
LOG:
!ENTRY org.eclipse.core.resources 4 376 2006-08-04
17:49:56.640
!MESSAGE Marker id: 680 not found.
!SESSION 2006-08-07
11:00:26.375
-----------------------------------------------
eclipse.buildId=unknown
java.version=1.4.2_09
java.vendor=Sun
Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32,
NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY
com.adobe.flexbuilder.editors.mxml 4 1 2006-08-07
11:03:41.328
!MESSAGE MXMLEditorViewManager: Couldn't determine
opened/hidden view
!ENTRY org.eclipse.core.resources 4 376
2006-08-07 11:13:38.968
!MESSAGE Marker id: 687 not found.
!ENTRY
org.eclipse.core.resources 4 376 2006-08-07 11:15:58.46
!MESSAGE Marker
id: 700 not found.
!ENTRY org.eclipse.core.resources 4 376
2006-08-07 11:23:39.203
!MESSAGE Marker id: 709 not found.
!ENTRY
org.eclipse.core.resources 4 376 2006-08-07 11:26:22.15
!MESSAGE Marker
id: 721 not found.
!ENTRY org.eclipse.core.resources 4 376
2006-08-07 11:26:22.187
!MESSAGE Marker id: 724 not found.
--- In [EMAIL PROTECTED]ups.com,
"Mike Britton" <mbritton72@...> wrote:
>
> As I was
editing my mxml, changing an attribute, Flex Builder hung and
> crashed.
When I rebooted it, the project kept throwing that annoying
> "compiler
problem markers" error.
>
> To fix it, I copied my relevant files
into another project. I think
> the project was corrupted from the crash,
but I'm not sure what
> element got corrupted.
>
> As a
result, I'll be periodically recreating my projects for things
> that are
really critical. Just thought I'd report this to the list.
>
>
> Mike
>
