JW Validate crashes my Finale
Moderators: Peter Thomsen, miker
-
- Posts: 668
- Joined: Wed Dec 28, 2016 1:37 pm
- Finale Version: Using 26, testing 27
- Operating System: Mac
This is the Wiki connected with that plug-in. It might have an answer to your problem.
::: Bill
Some Important Things...
Make sure to save the document before running a test on it.
Select only a couple of tests at a time, unless you have a very small document. Getting a huge list of potential issues often takes longer time to manage.
Use the Options dialog box to uncheck tests that you aren't interested in, or tests that result in lots of false positives.
Some tests only make sense in certain scope. For example, tonality needs to be checked for scores only, while page layout needs to be checked for parts as well.
An issue marked as “error” doesn't necessarily mean an error, if the “issue” is intentional.
If Run only Safe Tests is turned OFF in the options, make sure to not switch to any other program on the computer during the scan.
Use View HTML to view all currently reported issues in your web browser. The tables in that view will also display the details side-by-side with the issue.
Don't replace a machine scan with a manual check of the material. Use it as an additional tool.
::: Bill
Some Important Things...
Make sure to save the document before running a test on it.
Select only a couple of tests at a time, unless you have a very small document. Getting a huge list of potential issues often takes longer time to manage.
Use the Options dialog box to uncheck tests that you aren't interested in, or tests that result in lots of false positives.
Some tests only make sense in certain scope. For example, tonality needs to be checked for scores only, while page layout needs to be checked for parts as well.
An issue marked as “error” doesn't necessarily mean an error, if the “issue” is intentional.
If Run only Safe Tests is turned OFF in the options, make sure to not switch to any other program on the computer during the scan.
Use View HTML to view all currently reported issues in your web browser. The tables in that view will also display the details side-by-side with the issue.
Don't replace a machine scan with a manual check of the material. Use it as an additional tool.
Version 26.3 / 27.4 / Mac OS 10.15.5 Catalina
Finale user since the beginning of time.
Finale user since the beginning of time.
I have checked, and I'm using a 64-bit version of the plugin (version 1.01).
I have a couple of error reports that may be useful. They are in PDF format, but I can't seem to attach them to this message.
Here are a couple of relevant sections of the error text:
1)
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000072
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [31708]
2)
Crashed Thread: 13
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000028
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [31807]
I have a couple of error reports that may be useful. They are in PDF format, but I can't seem to attach them to this message.
Here are a couple of relevant sections of the error text:
1)
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000072
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [31708]
2)
Crashed Thread: 13
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000028
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [31807]