App crashes before returning results

[mikedowler]

Hi, I am trying this app (v.1.2) for the first time. On both M1 and Intel, the app just crashes out before returning any results. The log shows that a bunch of results have been collected, but they never get as far as being shown on screen. There are no obvious errors in the log.

[mikedowler]

Specifically, it seems to crash at the same point every time:

• I get a list of the ids and names for whatever I am searching (scripts, packages, etc)
• I then get a list of [get] log entries presumably indicating that the app has fetched details for each of these items
• Next I have a list of [getDetails] log entries with urls to each of the policies
• Finally, I get a single group of [getDetails] log entries relating to a single policy:

  Wed Nov 17 11:34:43 [getDetails] GET: https://redacted.com:8443/JSSResource/policies/id/1558
  Wed Nov 17 11:34:43 [getDetails] singleEndpointXmlTag: policy
  Wed Nov 17 11:34:43 [getDetails] menuIdentifier: Packages
  Wed Nov 17 11:34:43 [getDetails] case policy,computer_configuration - Policy Name: 2020 - Brand Deployment - Fonts installation

  and that is where the log ends. It seems to always be the same policy, and this isn't the first one listed in the URL list (it is third). Is there any way to increase the logging verbosity, and maybe find out why this item (or maybe the next one?) is failing?

[mikedowler]

This is what I see by filtering the main system log on "Object Info"

default 11:49:28.921227+0000    analyticsd  Received event: com.apple.stability.crash {"bundleID":"com.jamf.pse.ObjectInfo","bundleVersion":"1","exceptionCodes":"0x0000000000000001, 0x00000001046d0fd0(\n    1,\n    4369223632\n)EXC_BREAKPOINTSIGTRAP","incidentID":"8F1499A3-0AF6-4B69-B822-074F7D75DBAA","logwritten":1,"process":"Object Info","terminationReasonExceptionCode":"0x5","terminationReasonNamespace":"SIGNAL"}
default 11:49:28.921313+0000    analyticsd  Aggregated. Transform: StabilityCrashNumerator3 Dirty: 1 Event: com.apple.stability.crash {"bundleID":"com.jamf.pse.ObjectInfo","bundleVersion":"1","exceptionCodes":"0x0000000000000001, 0x00000001046d0fd0(\n    1,\n    4369223632\n)EXC_BREAKPOINTSIGTRAP","incidentID":"8F1499A3-0AF6-4B69-B822-074F7D75DBAA","logwritten":1,"process":"Object Info","terminationReasonExceptionCode":"0x5","terminationReasonNamespace":"SIGNAL","timestamp":1637149768921067}
default 11:49:28.921108+0000    ReportCrash Sending event: com.apple.stability.crash {"bundleID":"com.jamf.pse.ObjectInfo","bundleVersion":"1","exceptionCodes":"0x0000000000000001, 0x00000001046d0fd0(\n    1,\n    4369223632\n)EXC_BREAKPOINTSIGTRAP","incidentID":"8F1499A3-0AF6-4B69-B822-074F7D75DBAA","logwritten":1,"process":"Object Info","terminationReasonExceptionCode":"0x5","terminationReasonNamespace":"SIGNAL"}
default 11:49:28.921380+0000    analyticsd  Aggregated. Transform: StabilityCrashNumerator3WithBundleVersion Dirty: 1 Event: com.apple.stability.crash {"bundleID":"com.jamf.pse.ObjectInfo","bundleVersion":"1","exceptionCodes":"0x0000000000000001, 0x00000001046d0fd0(\n    1,\n    4369223632\n)EXC_BREAKPOINTSIGTRAP","incidentID":"8F1499A3-0AF6-4B69-B822-074F7D75DBAA","logwritten":1,"process":"Object Info","terminationReasonExceptionCode":"0x5","terminationReasonNamespace":"SIGNAL","timestamp":1637149768921067}

[mikedowler]

Object Info-2021-11-17-113443.ips.zip And a zipped copy of the crash report

[BIG-RAT]

Launch it from Terminal: /Applications/Object\ Info.app/Contents/MacOS/Object\ Info That may give me a better idea what's happening - thanks!

[dev-yeet]

what os are you running? i'm running Monterey 12.1 beta2 and get this error, but i also haven't used it in a few weeks.

In terminal i get:

menuIdent: scg

[1]    69653 illegal hardware instruction  /Applications/Jamf\ Utilities/Object\ Info.app/Contents/MacOS/Object\ Info

[BIG-RAT]

Looks like it's a result of the logout trigger being removed - working of the fix.

[mikedowler]

Looks to be working in 1.2.1 - thank you! I do get this pop-up at the end (after all the results have populated). Same when calling from command line (and no CLI messages relating to that)

[BIG-RAT]

Check v1.4.0 - let me know if the issue persists.