On Thu, Aug 23, 2012 at 11:11:43AM -0700, Silvio Levy wrote:
>
> > Translation: this problem would be a lot easier to solve if someone else
> > had it before me and documented the solution.
>
> Not sure why this deserves sarcasm.
>
> Is this really the first case of "Segmentation fault" that has come to
> the developers' attention?
>
> I can document the solution, if you'd like. (BTW you wrote "Maybe
> your profile got corrupted. Try a new profile." It's not obvious how
> you do this if you can't even get conkeror started. In the event I
> found /home/levy/.conkeror.mozdev.org/conkeror/profiles.ini and
> changed StartWithLastProfile=1 to 0. Not sure if that's the best way.)
>
> > I don't know what caused that segfault, but the error before it is
> > probably because you forgot to:
> >
> > require("content-policy");
> >
> > before using content_policy_hook in your rc.
>
> No - it's there (line 1 of my content-policy.js)
>
> Silvio
>
>
Sorry if that came off too harsh. Changing profiles is a very general
diagnostic step, not specific to segfaults, and to my knowledge, we have
seen no cases where changing profiles solved a segfault.
I'm out of ideas for your problem. It sounds like something is corrupted
somewhere. Reinstall everything, try different versions of xulrunner (or
firefox). Fresh profile. Maybe corruption in some other library that
xulrunner/firefox depends on?
--
John Foerch
_______________________________________________
Conkeror mailing list
[email protected]
https://www.mozdev.org/mailman/listinfo/conkeror
