[Android] Native SIGSEGV in `libpdfium.so` (`FT_Done_Face`) still occurring on `react-native-pdf@7.0.4

[Siddhantshelake]

Description

We are seeing a native Android crash in production that appears to originate from libpdfium.so.

The crash is a null pointer dereference (SIGSEGV) occurring in FT_Done_Face. We can confirm that this is still occurring after upgrading to the latest react-native-pdf release (7.0.4).

Environment

• react-native: 0.82.1
• react-native-pdf: 7.0.4
• react-native-blob-util: 0.24.9

Crash stack

null pointer dereference: SIGSEGV 0x0000000000000088

#00 pc 0x342ca4 FT_Done_Face libpdfium.so
#13 pc 0x31b00 Java_io_legere_pdfiumandroid_PdfPage_nativeClosePage libpdfiumandroid.so
#22 io.legere.pdfiumandroid.PdfPage.close
#26 io.legere.pdfiumandroid.PdfiumCore.renderPageBitmap
#28 com.github.barteksc.pdfviewer.PdfFile.renderPageBitmap
#30 com.github.barteksc.pdfviewer.RenderingHandler.proceed
#32 com.github.barteksc.pdfviewer.RenderingHandler.handleMessage

Steps to reproduce

We have not yet identified a deterministic reproduction path.

The crash is currently observed in production through Firebase Crashlytics while rendering PDF documents.

Expected behavior

PDF rendering should complete without crashing the native Android process.

Actual behavior

The Android application crashes with a native SIGSEGV inside libpdfium.so (FT_Done_Face).

Additional information

• Observed in production via Firebase Crashlytics.
• Still occurring after upgrading to react-native-pdf@7.0.4.
• The crash appears to originate from the underlying pdfium/pdfiumandroid layer during page rendering or cleanup.

Question

Is the FT_Done_Face / libpdfium.so SIGSEGV still considered an open issue, or is there a known fix or workaround available?