https://issues.apache.org/bugzilla/show_bug.cgi?id=46211





--- Comment #2 from ilj <[EMAIL PROTECTED]>  2008-11-14 10:30:21 PST ---
no, i didn't tried it - but it seems quite obvious.
and anyway - i will not be able to reproduce that easily for two reasons:

1. it happens only when two threads have failed to load the font properly,
which is seldom enough by itself. and this got to happen to those threads in
this special order - one thread faile, tried to call isFailedFont, but got
outrun by another thread which grabs the changeLock ...

2. the font loading issue, which causeв this bug in my case was quickly fixed.
and i really don't want to break that again :-)

so, i suggest changing the "if" and "synchronized" order as in my previous
comment AND making changeLock final and initializing it along with that.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to