Q: system profiler crash

System Profiler should not be in an El Capitan install. It may have been brought over with Migration Assistant.

Could be corrupt plist.  Try deleting the com.apple.SystemProfiler.plist

From Finder>Go>Go to Folder>  copy and paste:

~/Library/Preferences/com.apple.SystemProfiler.plist

delete this plist

and same here:

~/Library/Preferences/com.apple.SystemProfiler.plist.lockfile

delete this file  and restart your machine.

Both files will rebuild themselves on the reboot.

Maybe, but System Profiler is not compatible with El Capitan. System Information is however.

dialabrain wrote:

 

Maybe, but System Profiler is not compatible with El Capitan. System Information is however.

Are you certain?

system_profiler is the command line version (note the underscore & the path listed within /usr/sbin/)

I'm not in front of 10.11 so I can't check, however the command has existed for years on OS X, even on Macs that use 'System Information' app to list the output of that command.

The manual is at…

https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPag es/man8/system_profiler.8.html

Or use this in Terminal (without quotes)…

'man system_profiler'

…to view your local manual.

I'd remove all third party hardware (USB devices etc), reboot & try opening the report again.

You could also try running the command based on the listed arguments in the crash…

1. "/usr/sbin/system_profiler",
2.     "-nospawn",
3.     "-xml",
4.     SPDisplaysDataType,
5.     "-detailLevel",
6.     full
7. ), dataType: SPDisplaysDataType

I think that becomes this command…

/usr/sbin/system_profiler -nospawn -xml SPDisplaysDataType -detailLevel full SPDisplaysDataType

P.S.

I believe the hex numbers you refer to are the memory regions, as such they will differ when the OS loads it at different times.

Hi Drew, system_profiler is still in /usr/sbin but since the user mentioned System Profiler in "About This Mac" I assumed he has the System Profiler app still installed in Utilities. Another user had the same problem. I wasn't thinking about Terminal commands.

FWIW…

Thanks for confirming it still exists.

It's easy to conflate the old app with the command line tool. I suspect the System Information app calls the command to save on duplicated code.

no problem.

ok, good.

Have you removed all the third party hardware & retested?

You seem to have an Android device, a printer, a gaming mouse, multiple a storage devices connected…

Any one of which may cause issues with bad drivers or hardware with bad USB configuration.