Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

White Screen of Death (WSOD) After Migrating from Meteor 2.16 to Meteor 3.1.2 #13639

Open
Berchez opened this issue Feb 28, 2025 · 2 comments
Open
Labels
Meteor 3 relates to Meteor 3

Comments

@Berchez
Copy link

Berchez commented Feb 28, 2025

After migrating our application from Meteor 2.16 to Meteor 3.1.2, we are experiencing intermittent white screen of death (WSOD) issues. The errors appear to follow a pattern but are difficult to consistently reproduce. Sometimes, the application works, but after restarting or making changes, it breaks again with the same errors.

Observed Errors:

Depending on the state of the project, one of the following errors appears in the browser console:

  1. Uncaught TypeError: Cannot read properties of undefined (reading 'Kadira')
    print
    print2

  2. If we reinstall montiapm:agent (which uses Kadira), we get:
    Uncaught TypeError: Cannot read properties of undefined (reading 'CollectionHooks')
    print3
    print4

  3. If we reinstall CollectionHooks, we then get:
    Uncaught TypeError: Cannot read properties of undefined (reading 'Roles')
    (from meteor/roles package)
    print5
    print6

  4. If we reinstall meteor/roles, we loop back to the first error with Kadira.
    print7
    print8

This loop continues indefinitely.

Troubleshooting Attempts:

We have tried the following steps, but none have led to a permanent fix:

  • Removing and reinstalling node_modules and package-lock.json
  • Removing the meteor/local directory
  • Creating a fresh checkout of the repository (worked once but not consistently)
  • Uninstalling and reinstalling Meteor (npx meteor uninstall and then npx meteor)
  • Ensuring all developers in our team are using the same Meteor version and dependencies
  • Trying it on Mac, Linux, and Windows
  • Trying it on different browsers

Impact:

All developers in our project have encountered this issue. It makes it difficult to proceed with the migration since the issue occurs sporadically without a clear pattern.

Request for Help:

We are looking for guidance on how to diagnose and resolve this issue. Any insights into what might be causing the undefined errors and why the system sometimes works and sometimes breaks would be greatly appreciated.

Any help or pointers would be highly appreciated!

@StorytellerCZ
Copy link
Collaborator

You need montiapm:agent at version 3.0.0-beta.14

@StorytellerCZ StorytellerCZ added the Meteor 3 relates to Meteor 3 label Mar 1, 2025
@Berchez
Copy link
Author

Berchez commented Mar 3, 2025

@StorytellerCZ
I already had this version of montiapm:agent.

montiapm:agent@3.0.0-beta.14
matb33:collection-hooks@2.0.0
roles@1.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Meteor 3 relates to Meteor 3
Projects
None yet
Development

No branches or pull requests

2 participants