Project

Profile

Help

Bug #5158

closed

Saxon EE 9.9 and above NullReference Exception

Added by Vitaly Filatenko over 2 years ago. Updated over 2 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Multithreading
Sprint/Milestone:
Start date:
2021-11-10
Due date:
% Done:

0%

Estimated time:
Legacy ID:
Applies to branch:
10, 9.9
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:
.NET, Java

Description

Recently I has created a topic on Stack Overflow regarding to intermittent NullReference Exception caused by Saxon component (https://stackoverflow.com/questions/68922354/intermittent-error-there-was-an-error-while-attempting-to-compile-the-styleshee/68926635?noredirect=1#comment122554873_68926635).

Fortunately, I was able to create a test application which is able to reproduce this error 1 times from 5 (inversely proportional to a computer’s processing power). You can find it attached. Run it many times and occasionally you’ll get the error.

Some notes and observations: I was not able to reproduce is on simple test source, only on our production set of xslt files. Also the exception does not occur if I will not activate Saxon Processor (by commenting SaxonActivator.ActivateSaxonProcessor(Processor) line). The issue was introduced in Saxon 9.9, up to 10.5. Not reproduced for Saxon 9.7.

Please note, attached sources contain our license key, also sample xslt (WS_Single_Invoice-20210921.3.0.0) would not be published anywhere. So, please advice how I can safely attach mentioned sample to avoid unauthorized access over the Internet.


Related issues

Is duplicate of Saxon - Bug #5148: Multithreading issue during compilationClosedMichael Kay2021-10-28

Actions
Actions #1

Updated by Vitaly Filatenko over 2 years ago

Sorry, it can be closed as a duplicate for https://saxonica.plan.io/issues/5148

Actions #2

Updated by Michael Kay over 2 years ago

  • Status changed from New to Duplicate
Actions #3

Updated by Michael Kay over 2 years ago

  • Is duplicate of Bug #5148: Multithreading issue during compilation added

Please register to edit this issue

Also available in: Atom PDF