unless MuPDF is to be used purely in a single thread at a time.” MuPDF needs to protect against unsafe access to certain structures/resources/libraries from multiple threads. It does this by using the threads; this might give a small performance increase in single-threaded programmes, but will be unsafe in multi-threaded programmes. – Otherwise each thread has its own fz_context*. One can instead builds on Windows. – Fixed 32-bit builds on Windows. – Fixed cross-build to arm64 on MacOS. – Fixed unsafe custom fz_search_page2(). – Added custom fz_highlight_selection2(). – Added debug diagnostics to

unless MuPDF is to be used purely in a single thread at a time.” MuPDF needs to protect against unsafe access to certain structures/resources/libraries from multiple threads. It does this by using the threads; this might give a small performance increase in single-threaded programmes, but will be unsafe in multi-threaded programmes. – Otherwise each thread has its own fz_context*. One can instead

unless MuPDF is to be used purely in a single thread at a time.” MuPDF needs to protect against unsafe access to certain structures/resources/libraries from multiple threads. It does this by using the threads; this might give a small performance increase in single-threaded programmes, but will be unsafe in multi-threaded programmes. – Otherwise each thread has its own fz_context*. One can instead

unless MuPDF is to be used purely in a single thread at a time.” MuPDF needs to protect against unsafe access to certain structures/resources/libraries from multiple threads. It does this by using the threads; this might give a small performance increase in single-threaded programmes, but will be unsafe in multi-threaded programmes. – Otherwise each thread has its own fz_context*. One can instead