(In reply to Dana Keeler (she/her) (use needinfo) (:keeler for reviews) from comment #1) > Ryan - could this be due to the recent sqlite3 update in bug 1698592? Comment 0 suggests that this spike started about a week and a half after that update landed. In general, I'm having a difficult time discerning much of a spike though looking at the trends in prior releases. (In reply to Robert Relyea from comment #4) > What is surprising to me is that you are getting a crash in nss3.dll in sqlite code. This sounds bad. Are we really shipping two copies of sqlite these days? How can we confirm which version is even being built & shipped by NSS in that case?
Bug 1712118 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Dana Keeler (she/her) (use needinfo) (:keeler for reviews) from comment #1) > Ryan - could this be due to the recent sqlite3 update in bug 1698592? Comment 0 suggests that this spike started about a week and a half after that update landed. In general, I'm having a difficult time discerning much of a spike though looking at the trends in prior releases. (In reply to Robert Relyea from comment #4) > What is surprising to me is that you are getting a crash in nss3.dll in sqlite code. This sounds bad. Are we really shipping two copies of sqlite these days? I guess the stacks at least show the correct copy in third_party being used.