-
Notifications
You must be signed in to change notification settings - Fork 986
Closed
Description
Operating System
macOS
Browser Version
Chrome 124
Firebase SDK Version
10.11.0
Firebase SDK Product:
Auth
Describe your project's tooling
JavaScript (webpack) with 'firebase/auth/web-extension' import. Webpack config:
const path = require('path');
module.exports = {
entry: './src/js/firebase.js',
mode: 'production',
experiments: {
outputModule: true
},
output: {
library: {
type: 'module'
},
path: path.resolve(__dirname, 'src/resources'),
filename: 'firebase.js',
chunkFormat: 'module'
},
devtool: 'source-map',
target: 'webworker'
};
Describe the problem
When using getAuth to determine the loggedIn user, we are getting "Maximum call stack size exceeded" error.
Steps and code to reproduce issue
The issue only happened for 1 user so far, out of thousands of users. We are not sure what may have caused the issue. There are two stack traces (for the same user):
Stack trace 1 is:
RangeError: Maximum call stack size exceeded
at HeartbeatServiceImpl.triggerHeartbeat(./node_modules/@firebase/app/dist/esm/index.esm2017.js:704:5)
at ne(./node_modules/@firebase/app/dist/esm/index.esm2017.js:262:34)
at getAuth(./node_modules/@firebase/auth/dist/esm2017/index-4dc22a28.js:9474:22)
at loggedIn(./file2.js:13:12)
at <anonymous>(./file1.js:1123:29)
(file*.js are our package files)
Stack trace 2 is:
RangeError: Maximum call stack size exceeded
at HeartbeatServiceImpl.triggerHeartbeat(./node_modules/@firebase/app/dist/esm/index.esm2017.js:704:5)
at ne(./node_modules/@firebase/app/dist/esm/index.esm2017.js:262:34)
at getAuth(./node_modules/@firebase/auth/dist/esm2017/index-4dc22a28.js:9474:22)
at uid(./file2.js:22:10)
at readonlySubscription(./file2.js:472:44)
at unsubscribe(./file3.js:374:9)
at c.next(./node_modules/@firebase/firestore/dist/index.esm2017.js:19358:23)
at apply(./node_modules/@firebase/firestore/dist/index.esm2017.js:15696:27)
at sentryWrapped(../node_modules/src/helpers.ts:95:1)