New ValueTable entry with GPType parameter causes crash

[AustinMilt]

I wanted to post this to flag what I think is a bug.

I created a two-column ValueTable Parameter in a Python Toolbox where the second column is a GPType Parameter. When I go to add a new entry to the table (when the tool is open in ArcMap), the tool freezes and then any action (e.g. clicking) causes ArcMap to crash.

[ShaunWalbridge]

I can confirm this is a bug at 10.1SP1. I've made a simple Python toolbox to recreate the issue. It's the UC next week, so many of us will be traveling, but if you don't hear back soon, remind me to submit a bug report.

Here's the full Problem signature:

Problem signature:
  Problem Event Name: BEX
  Application Name: ArcMap.exe
  Application Version: 10.1.1.3143
  Application Timestamp: 5058f74e
  Fault Module Name: MSVCR90.dll
  Fault Module Version: 9.0.30729.6161
  Fault Module Timestamp: 4dace5b9
  Exception Offset: 00074361
  Exception Code: c0000417
  Exception Data: 00000000
  OS Version: 6.1.7601.2.1.0.256.4
  Locale ID: 1033
  Additional Information 1: 3694
  Additional Information 2: 3694321e13ff624a62165c908c6077b3
  Additional Information 3: 9413
  Additional Information 4: 941366b9226eef57f2089e0bc55a2c5f

cheers,
Shaun

[ShaunWalbridge]

Austin,

I've submitted a bug report on this issue.

cheers, Shaun

[AustinMilt]

Austin,

I've submitted a bug report on this issue.

cheers, Shaun

Thanks. Is there a way for me to do this in the future, or is it best for me to submit to the forum for all the world to see?

[ShaunWalbridge]

Is there a way for me to do this in the future, or is it best for me to submit to the forum for all the world to see?

Yes, you can submit issues by visiting http://support.esri.com and filing a bug there. Generally, most bugs get caught by the exception handling logic and you can directly report them from that application, but in this case the interaction is up the stack and ArcGIS doesn't 'see' the crash, so a support request is necessary.

[ShaunWalbridge]

Austin,

I can confirm this is fixed in 10.2 SP1 (10.2.1):
  http://support.esri.com/en/bugs/nimbus/TklNMDkzMjA0

cheers,
Shaun