1057581 - old profile crashes on startup [@ nsRDFPropertyTestNode::FilterInstantiations]

Status: RESOLVED INCOMPLETE

(SeaMonkey :: Startup & Profiles, defect)

Description

[kevink9876543]

Not sure if this is an issue with SeaMonkey or if something about my profile (copied from SeaMonkey 2.28 on a Mac) is the problem, but starting SeaMonkey (build from c-c rev aabbc0dc1a97 patched as suggested by Ian Neal so that make packages works / m-c rev c1e574f7a9a3) with my existing profile results in a crash.  I did submit crash reports, but there's probably no point linking them here as this is a self built SeaMonkey.
I got it working by starting in safe mode, telling it to make permanent only to disable all extensions, and then re-enabled all my extensions, but I shouldn't have to do that to be able to use my normal profile.

This wasn't the case in my last build (from c-c rev c8f5d9af8549 patched as above / unknown m-c rev).

Comment 1

[kevink9876543]

Official Linux i686 nightlies are back, so here's a crash report for this bug from official build 20140901003005:
http://crash-stats.mozilla.com/report/index/bp-57c17ce0-83d6-4f60-9fe9-86d792140901

Comment 2

[Philip Chee]

(In reply to kevink9876543 from comment #1)
> Official Linux i686 nightlies are back, so here's a crash report for this
> bug from official build 20140901003005:
> http://crash-stats.mozilla.com/report/index/bp-57c17ce0-83d6-4f60-9fe9-
> 86d792140901

Looks like a DUP from Bug 461695

Comment 3

[kevink9876543]

Maybe the same root cause? but not quite the same issue, because this wasn't happening until some ways into 2.31 nightlies, AFAIK I'm not loading any local HTML files on startup, and disabling then re-enabling all my extensions (which isn't mentioned at all in the other bug) works around it.

Comment 4

[kevink9876543]

This does not happen in a self build of today's code run straight from the objdir
???

(packaging is broken, so I can't package my build to check that, sorry)

Comment 5

[bz]

The comments in bug 1092810 (possibly a dupe of this one) have some more information on the latest recurrence of this bug that is affecting SM 2.31b1.

Comment 6

[kevink9876543]

Note: AFAICT this bug really is specific to Linux i686 builds (including running Linux i686 build on x86_64 Linux).  I do not get this issue with Mac OS X or Linux x86_64 builds of SeaMonkey 2.32 running on the respective systems.

Comment 7

[David E. Ross]

I observed this when updating from SeaMonkey 2.26.1 to 2.33 on each of four profiles.  On selecting the Restart SeaMonkey button, SeaMonkey then launched okay.  The about:crashes file has ID a53df760-07f6-49c2-a6f5-059982150311.

Comment 8

[Rainer Bielefeld]

This came up with 2.31 (or more early), this information in Version field is much more useful than "Trunk", for details see mozilla.dev.apps.seamonkey "Re: How to use Bugzilla-field "Version" - TRUNK"

Comment 9

[Rainer Bielefeld]

(In reply to David E. Ross from comment #7)
@David E. Ross:
This one has been considered a Linux Bug, did you add your comment here intendedly after checking other possibly related bugs?

Comment 10

[David E. Ross]

I am getting this under Windows 7 Ultimate SP1 (x64) with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 SeaMonkey/2.35.  The latest crash report with my primary profile has ID bp-315349b8-68ed-4c38-85f1-b03002150724.  

I seem to recall that I was informed that this bug report applied to my earlier crash cited in comment #7 even though this report was initially submitted only for Linux.

Comment 11

[kevink9876543]

(In reply to Rainer Bielefeld from comment #9)
> This one has been considered a Linux Bug,
@Rainer Bielefeld: Actually I'm not so sure about that - my earlier comment was based only on what OSes I have access to for this (Linux & Mac OS X).  I've seen indications elsewhere (can't remember where) that Win32 builds *are* affected by this bug... I think this bug is common to all 32-bit builds regardless of platform, but I didn't update the bug fields because, again, I cannot verify that for myself.  Sorry about the confusion.

Comment 12

[kevink9876543]

(oops, overwrote David E. Ross' change to the OS field)

Comment 13

[David E. Ross]

This problem did not occur when updating from the contributed version 2.35 to the official version 2.35.  This indicates that the cause is somewhere in a preference or capability that was identical between the contributed and official versions.

Comment 14

[kevink9876543]

(In reply to David E. Ross from comment #13)
> This problem did not occur when updating from the contributed version 2.35
> to the official version 2.35.
As expected - this bug is a crash when a profile that has not been used in *any* SeaMonkey version above 2.30, gets used in 2.31 or higher.  This bug does *not* apply to any profiles that have already been used in SeaMonkey 2.31 or later.  Whether or not the SeaMonkey build(s) are official is immaterial here.

Comment 15

[David E. Ross]

(In reply to kevink9876543 from comment #14)
> As expected - this bug is a crash when a profile that has not been used in
> *any* SeaMonkey version above 2.30, gets used in 2.31 or higher.  This bug
> does *not* apply to any profiles that have already been used in SeaMonkey
> 2.31 or later.  Whether or not the SeaMonkey build(s) are official is
> immaterial here.

Aha.  Yes, I did get the crashes (once each for multiple profiles) yesterday when updating my wife's PC from SeaMonkey 2.26.1 to 2.35.

Comment 16

[Martin Creutziger [:MMx]]

this bug is potentially a duplicate of bug 1092810

Comment 17

[kevink9876543]

(In reply to Martin Creutziger [:MMx] from comment #16)
> this bug is potentially a duplicate of bug 1092810
This bug is present only in 32-bit builds; the one you linked seems independent of build architecture.  Similar, but not a duplicate IMO.

Comment 18

[Mats Palmgren (inactive)]

FYI, bug 1254952 have repeatable steps-to-reproduce for this crash.

Comment 19

[Frank-Rainer Grahl (:frg)]

The affected rdf code has been replaced. I think we can close this one.