Martin Holmes

@joeytakeda Per Liam Quin on XML Slack: > If you're using an accumulator over a collection, beware of storing anything from individual documents as that will force the entire document...

Doesn't look like any pointers to nodes are being kept in the accumulator, just copies of strings, so that's not it. The only real differences between the 1.4 release branch...

@joeytakeda Well, here's a thing: I switched in Saxon 10, and with no other changes, the build works fine. So this is a problem with Saxon 12. Next I'll try...

Well, it seems to work fine in Saxon 12.8, the latest version. So I'm going to move the dev branch forward to 12.8.

Working on this in branch iss-323-update-saxon so I can test it properly -- a quick test caused an exception in the xml resolver, so I want to be a bit...

OK, tests are working in the branch. My next test will be to re-pull this branch's content to replace the BBTI staticSearch folder, and to run the BBTI build again....

Turns out it fails in 12.8 too. The success I thought I had may have been a fluke or an illusion. Testing again with Saxon 10 now.

The build works reliably with Saxon 10, but fails reliably (with one exception, which might have been a fluke) with Saxon 12.5 or 12.8. @joeytakeda I vote we revert to...

@joeytakeda I agree on testing Saxon 11, and the results will be interesting to see. If there were any history of vulnerabilities in Saxon 10 I would also be nervous...

@joeytakeda Tested with Saxon 11.7, and it works fine. So whatever the problem is, it was introduced with Saxon 12. Since 11.7 is still supported, we could move back to...