wu-hui

The firestore error here is similar to https://github.com/firebase/firebase-ios-sdk/issues/9995, i guess you cannot reliably reproduce this one?

It looks like the first crash is from crashlytics. The second one happens when firestore try to surface the document, and there are some malloc issue. Are you able to...

Firestore timestamp has to be `Range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z`, from https://firebase.google.com/docs/reference/swift/firebasefirestore/api/reference/Classes/Timestamp We will consider adding a convenient method to check if a given time is acceptable.

Thanks for report this and an awesome reproduction. I can confirm our memory usage is not ideal..I am not sure how to resolve this yet. I want to ask if...

Thanks. Just to let you know, it will probably take some time for us to come up with some way to mitigate this, it probably requires some significant changes. In...

After looking into your reproduction a bit closer, it seems the Javascript Heap memory usage is not the merit, somehow "page" uses most of the memory in your reproduction, which...

Do you mind help us do a profile on Chrome or Firefox on other platforms, to see if you observe high memory usage as well? They might be using a...

OK, I think at least we know this is an issue with Safari only. I'll do some research to see if there are similar issues reported before.

Hi @maccman Sorry for the late response. Unfortunately our own research found no clear way how we can fix this from the SDK side. I'd encourage you to file a...

@vojto That would also work, it is using the iOS SDK in this case. @maccman I cannot, sorry. We hold a bunch of objects in memory, and this is usually...