Instruments: Using a custom (DTrace) instrument prevents saving trace or quitting Instruments

Originator:quellish
Number:rdar://24329125 Date Originated:25-Jan-2016 11:17 AM
Status:Open Resolved:
Product:Developer Tools Product Version:Instruments 7.2 (7C68)
Classification:Crash/Hang/Data Loss Reproducible:Always
 
Summary:
When using a custom instrument (Dtrace instrument) for a trace the trace cannot be saved and Instruments will not quit. Instruments must be force quit and the trace data is lost.

Steps to Reproduce:
1. Open any iOS Xcode application project (or create a new one)
2. Command-i to profile.
3. Instruments opens, select "Blank" for the trace template.
4. From the "Instrument" menu, select "Build new instrument. You can build anything, attached is a screenshot of a simple instrument using an Objective-C system probe.
5. Start a trace.
6. End the trace.
7. Select "Save" or "Save As..." from the File menu.

Expected Results:
Trace saved! You can then quit instruments or close the window.

Actual Results:
Instruments just beeps at you and does not save. Attempting to quit Instruments has the same effect and does not quit. Attempting to close the window has the same effect.

Version:
Instruments 7.2 (7C68)
Xcode 7.2 (7C68)
MacOS 10.10.5 (14F1605)

Notes:
Happens with any custom instrument, any probe used.

Configuration:
  Model Name:	MacBook Pro
  Model Identifier:	MacBookPro6,2
  Processor Name:	Intel Core i7
  Processor Speed:	2.66 GHz
  Number of Processors:	1
  Total Number of Cores:	2
  L2 Cache (per Core):	256 KB
  L3 Cache:	4 MB
  Memory:	8 GB
  Processor Interconnect Speed:	4.8 GT/s
  Boot ROM Version:	MBP61.0057.B0F
  SMC Version (system):	1.58f17
  Serial Number (system):	W80162SEAGZ
  Hardware UUID:	13AC6D87-DD19-50A0-8A68-E150C94A095F

Attachments:
'custom instrument.png' was successfully uploaded.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!