Bug 255013 – Speculative fix for crash mitigation in JSModuleRecord::instantiateDeclarations

• Status: RESOLVED
• Resolution: FIXED
• Component: JavaScriptCore

[Yijia Huang]

...

[Yijia Huang]

<rdar://107634974>

[Yijia Huang]

Pull request: https://github.com/WebKit/WebKit/pull/12398

[EWS]

Committed 262608@main (79f077301b07): <https://commits.webkit.org/262608@main>

Reviewed commits have been landed. Closing PR #12398 and removing active labels.

[Mark Lam]

<rdar://107531050>

Hi, I encountered the error "Importing module xxx is not found." in our project. Most of the devices experiencing this issue are running iOS 16.5/6/7. I found this commit in the WebKit repository; it seems that this error was a bug present in WebKit for a period of time. I would like to understand the cause of this error and how it was fixed, but my attempts to search the repository have been unsuccessful. I hope someone can provide some information to help us avoid similar issues in our production environment. Thanks!

[Yijia Huang]

Hi, could you please file another bugzilla with a repro case? Please include the detailed repro steps and configuration and system of the devices. Thanks.

Hi,

Thank you for your response. I want to provide some more context regarding the issue. The error "Importing module xxx is not found." occurs exclusively for users on iOS 16.5, 16.6, and 16.7. Based on our observations, approximately half of these users encounter the error during their visits.

It's important to note that users on iOS 17 and above do not experience this error, suggesting that iOS 17 has either fixed or worked around the issue.

I'm sorry that given the complexity of our project and recent significant changes, we are currently unable to provide a minimal reproducible demo without exposing sensitive business logic. If there are any related resources or documentation you could share, it would be greatly appreciated as we work to address this issue.

Thank you for your understanding!