Fixing Fatal Process Aborts in TensorFlow Lookup Tables

Description and use

Fixing fatal crashes in TensorFlow lookup table exports by adding signature validation before tensor allocation.

Problem

Calling TensorFlow lookup table export operations with mismatched data types causes an immediate SIGABRT crash, preventing graceful error handling.

Outcome

Implemented signature validation in LookupTableExportOp, preventing hard crashes and enabling proper error propagation.

Workflow

• 1. Define a StaticHashTable with int64 keys and values.
• 2. Attempt to export the table using tf.raw_ops.LookupTableExportV2 with Tkeys/Tvalues set to tf.string.
• 3. Observe the process abort due to a CHECK_EQ failure.
• 4. Apply the patch adding MatchSignature to LookupTableExportOp.
• 5. Re-run the export; now an InvalidArgumentError is raised.
• 6. Add a unit test to ensure signature mismatches are caught.

Evidence

LookupTableExportOp never verified signatures. It immediately called table->ExportValues(ctx).

Source

The fix was straightforward and matches the pattern established across all other lookup table kernels in lookup_table_op.cc.

Source