Crash after i long time browse on Facebook and close SeaMonkey

UNCONFIRMED
Unassigned

Status

SeaMonkey
General
UNCONFIRMED
3 years ago
2 years ago

People

(Reporter: Sladky Vladimir, Unassigned)

Tracking

SeaMonkey 2.39 Branch
Unspecified
Windows 10

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(4 attachments)

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39a1
Build ID: 20150806070100

Steps to reproduce:

I browse (long time only) on Facebook and close SeaMonkey.


Actual results:

SeaMonkey closed too long time with CPU use 50% and after crashed (in safe mode too).
https://crash-stats.mozilla.com/report/index/8ac58cee-0a5e-4328-b0af-07f342150808

My selfcompiled x64 build crashes too:
https://crash-stats.mozilla.com/report/index/cedd4bb5-de58-46b1-85a5-8dd062150808

AbortMessage: [2208] ###!!! ABORT: file c:/builds/slave/c-c/build/mozilla/toolkit/components/places/Database.cpp, line 600

  if (shutdownPhase) {
    DebugOnly<nsresult> rv = shutdownPhase->AddBlocker(
      static_cast<nsIAsyncShutdownBlocker*>(mConnectionShutdown.get()),
      NS_LITERAL_STRING(__FILE__),
      __LINE__,
      NS_LITERAL_STRING(""));
    MOZ_ASSERT(NS_SUCCEEDED(rv));
  }
}



Expected results:

Not crash after i browse (long time) on Facebook and close SeaMonkey

Comment 1

3 years ago
NOT reproducible with  SeaMonkey en-US 2.39a1 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0 from official download area)  Gecko/20100101  Firefox/42.0  Build 20150806070100  (Classic Theme) on German WIN7 64bit

1. After login I opened 20 arbitrary Facebook pages in different TABs
2. After 30 minutes I clicked through all TABs, afterwards opened 10 additional
   facebook pages, most of them facebook settings of my  profile
3. After 65 minutes I again clicked thorugh all open TABs - no crash.

No Crash.

@Reporter: Please contribute a precise step by step instruction how to reproduce your problem.
Does the problem also appear in safe mode without active add-ons?
Flags: needinfo?(vlposta)
(Reporter)

Comment 2

3 years ago
Crashed with SeaMonkey en-US 2.39a1 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0 from official download area too.

I cannot specify time - if short time on Facebook, then not crashed if SeaMonekey close, if more minutes (one TAB only too) and more scrool facebook page crashed if SeaMonkey close.
Now i create places.history.expiration.transient_optimal_database_size and set it to 3 only and one day not crashed - maybe problem with save huge history and i need save all my history from 1.3.2015 (this is problem in new firefox vesion if browser.history_expire_days now not accepted and mus always backup and restore places.sqlite if my old history is automaticaly deleted ...)
Flags: needinfo?(vlposta)
(Reporter)

Comment 3

3 years ago
Created attachment 8646106 [details]
Crash after i browse on Facebook and close SeaMonkey

Crash after i browse on Facebook and close SeaMonkey
(Reporter)

Comment 4

3 years ago
Created attachment 8646109 [details]
Crash after i login to Bugzilla

Crash after i login to Bugzilla - same crash if i search on Google (in version with Debug info only)
(Reporter)

Comment 5

3 years ago
Created attachment 8646119 [details]
Search on Google crash

Search on Google crash
(Reporter)

Comment 6

3 years ago
Created attachment 8646120 [details]
Add Attachment to Bugzilla site crash

Add Attachment to Bugzilla site crash
(Reporter)

Comment 7

3 years ago
This crasches in version with debug info (only) a i cannot use this version to find other crashes and errors ... :-(

Comment 8

3 years ago
I modify OS due to user story.

@reporter:
I doubt that more and more lists are useful, we still need a step by step
instruction how to reproduce a crash. That might start with "download version with debug info from ..."
Flags: needinfo?(vlposta)
OS: Unspecified → Windows 10

Comment 9

3 years ago
At mozilla.support.seamonkey user Ed Mullen in thread "Windows 10 and SM crashes" complained of many SeaMonkey crashes under WIN 10.

So the best instruction how to reproduce these bugs might start with "Install WINDOWS 10"?
Flags: needinfo?(vlposta)
(Reporter)

Comment 10

3 years ago
I send more reports from various crashes on various situation (descripted "step how to reproduce" from "Crash file names" ...) if i have (in version vith debug info only) crashes in various situation a i cannot identify main problem with crash after brovse on Facebook and close SeaMonkey - momentaly O.K., but i need (funfional) version with debug info to identify (next) other problems too ...

This version (with debug info) is my selfcompiled X64 and i run it on Windows 10 x64 Home(same problems with debug info version in old Windows 8.1 before i upgrade to Windows 10)
http://web.quick.cz/vs165/TMP/W10Muj.png
Now i have two latest versions 2.40a1 x64 with (and without) debug info for normal use ...

I have questions - how to please i add options to .mozconfig for versions with debug symbols for sources visibility on sended crash to Bugzilla and for analyze crash dumps *.dmp in Debugging Tools for Windows ???

If i add "ac_add_options --enable-debug-symbols" only, then this option has no effect and i not see source files in crash sended to Bugzilla and in Debugging Tools i too not se source files (if i analyze crash dumps ) ... :-(

If i add "ac_add_options --enable-debug", then have this "console" version SeaMonkey (with this reports), but crashes in various situation ...

If i use 32 bit version from http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/ (for me is better x64 version and test it), i cannot debug crash dumps with source files in Debugging Tools with this version ...
(Reporter)

Comment 11

3 years ago
After i browse long time on Facebook and restart SeaMonkey:

AbortMessage: [6684] ###!!! ABORT: NULL actor value passed to non-nullable param: file c:\users\vlada\comm-central\obj-x86_64-pc-mingw32\ipc\ipdl\PImageBridgeChild.cpp, line 3073

https://crash-stats.mozilla.com/report/index/c6d71cd0-9bb9-451c-856b-8106e2150823
You need to log in before you can comment on or make changes to this bug.