--- Comment #4 from Alex Giotis <> ---
Gareth, I believe that this is a bug exposed by fixing some equals/hashcode
implementations. Those changes were introduced during the refactoring of
PropertyCache (as you wrote) and I also believe that the usage of Vectors is
problematic. I would prefer to have UnmodifiableLists (or some other immutable
structure) containing trimToSize() ArrayLists to minimise memory requirements.

With my previous comment, I was asking for an XSL:FO that has the potential of
triggering this deadlock. To reproduce it, one would need to render it
concurrently by different threads, probably connect a debugger and put some
breakpoints or change code to add some delays.

I understand that this is not always easy as one may need to anonymise the
input. I guess I would see blocks like:

<fo:block font-family="Arial" font-size="12pt">
<fo:block font-size="12pt" font-family="Arial">

but the effort to fix it would be wasted if this is wrong.

You are receiving this mail because:
You are the assignee for the bug.

Reply via email to