MozillaZine

Crash report not sent

Discussion of bugs in Seamonkey
TPR75
 
Posts: 973
Joined: July 25th, 2011, 8:11 am
Location: Poland

Post Posted February 29th, 2020, 5:43 am

Today I've updated SeaMonkey 2.49.5 x64 PL to newest (Build identifier: 20200222183812) version 2.53.1 x64 PL (I made backup of all profiles, of course). It looked like everything was correct... until sudden crash happened. E-mail (M&N part) was minimized and in Browser were two tabs: one with my "home website" (about:mozilla) and second with this forum ("General" sub-forum exactly). When I closed second tab (with "Ctrl+W") SeaMonkey 2.53.1 crashed.

Oh, well. It happens. So I choose to send Crash Report. Everything was marked as it should, my e-mail address was added (just in case) but this time I decided to add comment (about when/where is happened) and I choose to not restart SeaMonkey but to close it. To my surprise it wasn't sent - in "about:crashes" this one was marked as unsent.

I've searched through "Crash Reports" folder and:
1) "LastCrash" file has date of this crash and inside is value "1582977184",
2) "submit.log" file has date of this crash (+ one minute) with text inside "[Sat Feb 29 12:54:19 2020] Crash report submitted successfully",
3) "submitted" folder doesn't show file with this crash report,
4) "pending" folder shows two files (DMP and EXTRA types) with name (ID) of this unsent crash "3aa94aac-119b-4b26-826f-54ea8261990a",
5) manual search by ID or by prepared URL show nothing but errors: "No results were found" and "Invalid crash ID".

To me it (Crash Report not sent) looks like some kind of bug.

Is it possible to send unsent crash report?

TPR75
 
Posts: 973
Joined: July 25th, 2011, 8:11 am
Location: Poland

Post Posted February 29th, 2020, 7:19 am

TPR75 wrote:Is it possible to send unsent crash report?


On page "about"crashes" I can't open unsent report by clicking LMB (without or with Ctrl). I can click RMB and from context menu choose "Open Link in New Tab" (or "[...]Window"). I can click MMB (Middle Mouse Button) to open it in new tab.

Image

Unsent report links to:
https://crash-stats.mozilla.com/about/throttling/
... and there is such information:
If you'd like to see your crash report, type about:crashes into your location bar and your report will be automatically submitted to our server where we'll give it priority processing.


Well... it doesn't work... :(

frg
 
Posts: 982
Joined: December 15th, 2015, 1:20 pm

Post Posted February 29th, 2020, 11:55 am

Looks like our mozilla "friends" are at work again:

https://bugzilla.mozilla.org/show_bug.cgi?id=1604848

submit fails silently because of this server rule:
https://imgur.com/a/rPqRbpq

Not sure if we can restore it fast. We might need our own server. If you want you can zip it up and send it to me. Was this the first run after migration? I usually close SeaMonkey then. Bad things seem to happen otherwise.

FRG

TPR75
 
Posts: 973
Joined: July 25th, 2011, 8:11 am
Location: Poland

Post Posted February 29th, 2020, 1:12 pm

frg wrote:If you want you can zip it up and send it to me.


OK, sent already.

frg wrote:Was this the first run after migration? I usually close SeaMonkey then. Bad things seem to happen otherwise.


Of course it was not first run. Even not second. I checked few things before I started regular use. But I noticed in past that within first few runs SeaMonkey can crash. But reports were successfully sent back then.

therube

User avatar
 
Posts: 20551
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted March 1st, 2020, 7:22 am

If you submit the crash report - from within a running instance of 2.49.5, does the (2.53.1) crash get submitted?


The SeaMonkey specific Bug 1608976 - end accepting crash reports for SeaMonkey (September 2020).
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript

TPR75
 
Posts: 973
Joined: July 25th, 2011, 8:11 am
Location: Poland

Post Posted March 1st, 2020, 3:48 pm

therube wrote:If you submit the crash report - from within a running instance of 2.49.5, does the (2.53.1) crash get submitted?


The SeaMonkey specific Bug 1608976 - end accepting crash reports for SeaMonkey (September 2020).


Crash Report was submitted:
https://crash-stats.mozilla.com/report/ ... 9420200301
... but workaround so far is "classified".

Crash was caused by extension "MinimizeToTray revived 1.3.2":
https://addons.thunderbird.net/pl/seamo ... y-revived/
This latest version have some function related to tray icon (with context menu) but it was partially broken under 2.49.5 and not working at all under 2.53.x.

Now I'm using older version 1.1.2.1:
https://addons.thunderbird.net/pl/seamo ... d.1-signed
... and so far so good.

BTW MinimizeToTray Reanimated 1.4.11:
https://addons.thunderbird.net/pl/seamo ... eanimated/
... doesn't work at all - I can't minimize to tray any window.

TPR75
 
Posts: 973
Joined: July 25th, 2011, 8:11 am
Location: Poland

Post Posted March 14th, 2020, 12:51 pm

Another crash but this time it was sent automatically, without workaround:
https://crash-stats.mozilla.com/report/ ... bb10200314

It happened during browsing Google Maps (zooming in/out and dragging).

Does it mean SeaMonkey community have a deal again with people from Mozilla Crash Reports?

therube

User avatar
 
Posts: 20551
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted March 19th, 2020, 8:37 am

That one mentions nvidia, so might have a look at your video drivers.
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript

Return to SeaMonkey Bugs


Who is online

Users browsing this forum: No registered users and 2 guests