Critical UI Unresponsiveness and Runtime Errors in Looker Studio (BigQuery Connector)

Data Studio Data Studio Q&A
,
1

Hello,

I am reporting a critical issue where the Looker Studio report becomes unresponsive and triggers continuous JavaScript errors during interaction.

1. Problem Description:

  • Data Source: Google BigQuery

  • Symptom: In the report editor, clicking or selecting a ‘Dimension’ for a chart has no effect. The UI is completely frozen/unresponsive for these actions.

  • Runtime Error: Every time I click on the report view, a background request is sent to the jserror endpoint.

2. Error Details:

  • Console/Network Error: Cannot read properties of null (reading 'getContainerWrapper')

  • Firestore Error (previously noted): FIRESTORE (12.6.0) INTERNAL ASSERTION FAILED: Unexpected state (ID: b815)

3. Specific Error URLs for Debugging:

  • JS Error Link: https://lookerstudio.google.com/jserror?script=...&error=Cannot%20read%20properties%20of%20null%20(reading%20%27getContainerWrapper%27)&line=Not%20available

  • Affected Report: https://lookerstudio.google.com/u/0/reporting/341e6367-a1eb-4cd1-bf65-241dc63448ea/page/p_02rfl7na1d/edit

4. Observations: This seems to be a client-side rendering issue where Looker Studio fails to identify the container for the charts, possibly due to a conflict with the internal Firestore state or a breakdown in the BigQuery schema mapping.

I have already attempted hard refreshing and incognito mode, but the errors persist. Could you please investigate if there is a known bug regarding getContainerWrapper null errors in the current version?

Best regards,

1 Like
2

Hi @Scott_Ji Since the issue also occurs in incognito mode, it is likely not caused by extensions. The getContainerWrapper null error together with the Firestore assertion usually indicates a corrupted report state rather than a BigQuery connector problem. Try making a copy of the report and see if the copy works. Also create a new blank report with the same BigQuery source and add a simple chart to check whether the issue reproduces. If the new report works, gradually reintroduce calculated fields, blends, or filters to identify the trigger. If the error also occurs in a minimal setup, submit it via Help → Report a problem in Looker Studio and include the report ID and browser details so the team can review backend logs.

1 Like