does crash reporting - ah, maybe because it's a wg9s build... if so, i can fire up a Release & send... ?

Release looks to need a un/pw to submit a crash?

ah, that only happens if you try to "open" (Report) the link in a new tab

clicking directly on the link works

"works". worked for 2 older crashes (probably immaterial, & they were old), but not on today's crash?

and even with the ones that did go through, seems there isn't really much "there"

therube symbols probably missing currently. Still working some kinks out. If you have something reproducible best to try with the official beta.

no, it was just something out of the blue, totally unexpected, & it was that that made say, "hey i wonder what the report might show"

i've not crashed in ages. & the two that did go through, while i don't remember any details, it was most likely something i did knowingly & purposely, so the fact that i might have crashed was immaterial as i knew i was going to - ahead of time

therube Windows 10 19045 ?

Win7 SP2 :-)

therube which id?

frg_Away: cf34310f-acd0-4a3d-95ff-33ce18386c82

therube this is an old one.

not bugsplat

heh, ah, you're right. it was the one that was left under Report rather then submit

so it is then either

or

these are both old ones

& it's going to be the 1st one - cause that is 2.53.18

Not the beta for sure.

This is one I did intentionally with the beta:

SystemMemoryUse 53%, that seems odd

What is you build id?

frg_Away: not sure offhand (as i put in 2.53.19 after it happened) - actually i can probably tell - in a moment or two...

The ones above are ancient 2.53.17 and 2.53.18

frg_Away: well the 1 report shows, 20230609110002, so that should be Jun 9

yes ancient :)

you're right, old. unless that happened to be an old report, not sure now?

maybe a report did not get generated at all this time? & i simply took the 3 that did show as "2 are old" & 1 was the actual crash from today, so thought i'd just submit all of them, not paying attention to what was actually there?

i do have other 2.53.18's - of 07-02 09-17 & 10-01, & i've got to assume that if i downloaded them, i did actually install them? so that would point to a build of 20231001210003

but then, crash reporter certainly did come up.

frg_Away: i think i missed 1, it must be this, crash-reports-test.seamonkey-projec…8acf476-5198-4d6b-9d0a-7acd40231116

therube Anything going to crash-reports is/was old. Early October build 20231001210003

missed one that did in fact get submitted (just didn't realize) - again there were 3 & i saw 1 left (that didn't go through), so i only looked a 1 + 2 more - ignoring the fact that 3 did go through

yes, that was my last build prior to getting 2.53.19

therube maybe grab the current 2.53.19 then. Just updated nss and nspr and could use some testing.

i've not manually deleted that 1 old "stuck" crash report if i happen to crash again, that won't be there to confuse me

frg_Away: yes, i'm on that now

20231116140004

Probably good. The ones from today. Should show NSS 3.90 not 3.79.4 in about:support

yes, 3.90

maybe that's why i can't log in to gmail !!!

(or, could it be that i've forgotten the passwword ;-)

not to mention, that the reason for all of this is that they're doing away with "Basic" gmail - which is all i ever use. so on that note, i might just do away with them.

"Time to use the latest Gmail" - bla!

first (gmail) pop stopped working in Eudora. now they're getting rid of Basic webmail. hmphf.

therube all for the good of humanity I am sure.

or better data scraping & tracking

stupid crap. so gmail sends a "code" (or prompt) to my brothers phone (i have none) & he types in the code which i am reading into his phone, at which point i theoretically should be "in", but i'm not. so i go through the same nonsense 3 more times, & it was on the 4th that my end finally said "did you enter the code on your phone" & on clicking 'yes' on my end, so now i can get into gmail...

...- for now.

here's another one, secure.login.gov that is going to be a winner. login.gov. now what could possibly go wrong.

had a login for eftps.com. first have to go through login.gov. had a login for ssa.gov. first have to go through login.gov. but that doesn't work - because they have to send a code - via postal mail (usps, 5-7 days ;-))