Fix COMPOSITION_IMPL inspector for new Compose state field structure
Fixes NullPointerException when analyzing heap dumps from newer Compose versions where CompositionImpl uses "state" int field instead of "disposed" boolean field. The inspector now gracefully handles both field structures: - Old Compose: disposed boolean field (backward compatibility) - New Compose: state int field with values RUNNING=0, DISPOSED=3, etc. - Edge case: neither field exists (graceful fallback) Before: NullPointerException at AndroidObjectInspectors$COMPOSITION_IMPL$inspect line 792 After: Analysis completes successfully with proper state detection Fixes: https://github.com/square/leakcanary/issues/2781 Co-Authored-By: Claude <noreply@anthropic.com>
P
pblundell committed
58a5c1cc67893e3c45bf6c348a06531e901bd31c
Parent: 6de01db