12-02-2020 03:07 PM
David,
See Craig's answer in this same thread above.
Short story: you need to change com.mycompany.myapp to your app's "internal name" (bundle identifier), which is specified in your LabVIEW app's build specifications (in the LabVIEW Project).
12-02-2020 03:10 PM
Yes, I used the Internal Name.
12-02-2020 03:14 PM
Process: ClockLab Analysis [18350]
Path: /Users/USER/Desktop/*/ClockLab Analysis.app/Contents/MacOS/ClockLab Analysis
Identifier: ClockLabAnalysis
Version: 1.0.0.155 (1.0.0)
Build Info: lvapp-300001~0
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: ClockLab Analysis [18350]
User ID: 504
Date/Time: 2020-12-02 12:38:58.108 -0800
OS Version: macOS 11.0.1 (20B50)
Report Version: 12
Anonymous UUID: 2BB81ECB-2666-BF47-2A21-037AEAB41610
Time Awake Since Boot: 170000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [18350]
Application Specific Information:
Attempt to pop an empty graphics context stack.
Internal name is ClockLabAnalysis
Commands used:
defaults write com.actimetrics.ClockLabAnalysis NSGraphicsContextAllowOverRestore -bool YES
defaults write com.actimetrics.ClockLabAnalysis NSViewAllowsRootLayerBacking -bool NO
Errors:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.AppKit 0x00007fff22c4dbc1 +[NSGraphicsContext _popGraphicsContext] + 203
1 com.apple.AppKit 0x00007fff22c4dae1 +[NSGraphicsContext restoreGraphicsState] + 22
2 com.ni.labviewRuntime 0x00000001094c9ab1 WSetClipRgn + 417
3 com.ni.labviewRuntime 0x000000010943a743 ISetGPort + 627
4 com.ni.labviewRuntime 0x00000001094cda3a WSetPort(Wind_t**) + 138
5 com.ni.labviewRuntime 0x00000001094cc1b7 WSetBounds(Wind_t**, Rect, int, int) + 871
6 com.ni.labviewRuntime 0x00000001094cb5f9 WSize + 169
7 com.ni.labviewRuntime 0x00000001088e01e8 HeapUpdateWindowStyleCore(ObjectHeap*, ExecutionStateChange, Wind_t**, int) + 3288
8 com.ni.labviewRuntime 0x00000001088dcec0 DrawLocalVIState::DrawSetVIActive(VirtualInstrument*)
12-02-2020 03:14 PM
Can you post the error log of the crash? This will contain the bundle name, to confirm the exact command that should be executed.
12-02-2020 03:21 PM
If the internal name is ClockLabAnalysis I think you need to use the following commands:
defaults write "ClockLabAnalysis" NSGraphicsContextAllowOverRestore -bool YES
defaults write "ClockLabAnalysis" NSViewAllowsRootLayerBacking -bool NO
The quotes are optional, since no spaces, but I've added them so that others who copy+paste this might need them for their own application.
12-02-2020 11:22 PM
It worked! Thanks so much.
David
12-03-2020 02:25 PM
@FlatCat wrote:
It worked! Thanks so much.
That's great! However, it means you are using just "ClockLabAnalysis" as your Internal Name, and this violates the conventions of a bundle identifier, which is always a tuple in reverse DNS notation.
You should probably use something like "com.actimetrics.ClockLabAnalysis" for both the Internal Name in the build spec and the argument to the two 'defaults write' commands, just to be standards-compliant.
12-03-2020 03:43 PM - edited 12-03-2020 03:43 PM
@Craig_S. wrote:You should probably use something like "com.actimetrics.ClockLabAnalysis" for both the Internal Name in the build spec and the argument to the two 'defaults write' commands, just to be standards-compliant.
Thanks for that info. I wasn't really clear to me (and maybe others) this was a standard when filling out the build specification in LabVIEW.
12-04-2020 04:13 PM
I figured I would post a LabVIEW bug (and a work-around) I found on Big Sur:
12-11-2020 04:07 PM
I solved the problem using two following commands:
defaults write "com.ni.labview" NSGraphicsContextAllowOverRestore -bool YES
defaults write "com.ni.labview" NSViewAllowsRootLayerBacking -bool NO
https://support.vipm.io/hc/en-us/articles/360052653212-VIPM-2020-1-Crashing-on-macOS-11-Big-Sur-