702489 - Persistent crash since the 8.x Update on existing and fresh installations

Status: RESOLVED DUPLICATE of bug 691271

(Firefox :: General, defect)

Description

[GµårÐïåñ]

User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.2 (KHTML, like Gecko) Comodo_Dragon/15.0.3.0 Chrome/15.0.874.102 Safari/535.2

Steps to reproduce:

I began using my profile as I normally do and then I got the notice that there is a version 8 update available and its recommended that you apply this update. I said ok and it began doing its thing.


Actual results:

The updater downloaded, installed and even ran the add-on checker and when all was done and I clicked finish. It started the browser and nearly as soon as it painted on the screen, it said (Not Responding) briefly and then crashed popping up the crash reporter.


Expected results:

I expected nothing unusual from other past updates that had been done in the same manner and open up just fine and life goes on. But it didn't do that, not it persistently and without fail will crash on EVERY start, regardless of profiles, and even using a brand new profile, it will crash. In fact, when it reaches the profile selector window, if you pick quickly, it will briefly attempt to load before it crashes. However, if you sit on the profile selector for 15-45 seconds, it will itself show (Not Responding) and then immediately crash.

Comment 1

[GµårÐïåñ]

Here is the link to the last crash report I submitted. I have submitted many since this problem started happening few days ago but this is the last one, including the clean and complete removal and reinstall only to get the same result. If it helps anyone it has pretty extensive information about the state of the application and the system its on.

https://crash-stats.mozilla.com/report/index/bp-1131d7a3-5884-4193-a7d5-9c9a52111114

Comment 2

[GµårÐïåñ]

Bug: 691271 that is referenced at the bottom of the above crash report link (https://bugzilla.mozilla.org/show_bug.cgi?id=691271) does not accurately reflect my system. I have the latest version of RoboForm and I do not have the Fx adapter for it installed by choice. So the issue does not track with this problem I am having, as the conditions are not correlated, just the library files were similar in names.

Comment 3

[Marcia Knous [:marcia]]

I see 7.6.0.0 listed for Roboform in your report, but the latest version on their site is 7.6.3. Does the crash happen with that version?

RapportTanzan8.DLL has also been implicated in crashes, and that is in your module list as well.

Comment 4

[GµårÐïåñ]

(In reply to Marcia Knous [:marcia] from comment #3)

I am sorry that I couldn't get back to you sooner, dealing with some health issues. Now down to business.

As of when the update happened and the program started having issues I had the latest version which you got correctly 7.6.0 but you are right, I noticed they posted a 7.6.3, so not sure, will try and see what happens. Will report back in a few minutes.

As for the Rapport, yes that has been installed for a LONG time, since 3.x branch and has been there at each update and has been self updating along the way just fine and as far as I know, its not an issue with their software, but I wrote them to ask specifically so I can answer you and I am waiting on a reply, will let you know.

Comment 5

[GµårÐïåñ]

(In reply to Marcia Knous [:marcia] from comment #3)

Ok, here is the promised update. I installed the updated 7.6.3 and it went ok and then I tried to open up my Fx only to find some seriously bizarre things that I have a high level of doubt are related to the RF update.

First issue: The browser came up and tells me that its not the default, wrong, but I said ok make yourself default.

Second issue: The interface looked WRONG and when I dug deeper found that ALL of my addons were disabled and so I figured, ok, let's enable them and sat there enabling them all and restarted Fx.

So far annoying but not earth shattering. Until I realized when it came back that ALL THE options set for all the addons and even Fx itself for that profile were gone. All the contents of the Prefs.js were replaced with a default one and all the addons were back to their default state.

I compared the prefs.js now with the one backed up for that profile before, and they are COMPLETELY different. So this profile is pretty much toast, because even when I replaced the prefs.js with the previous one, it kept discarding it (and no I didn't do it while open and I did not cut and paste, I replaced the file when the browser was closed).

So I had 2 other profiles that I have used for ages and tried with them and got the exact same thing. I mean seriously at this point the only thing it allows me to do is recreate my profiles and start over again, it is completely ignoring, discarding and replacing past settings and profile options on each start, any idea what's going on there?

Comment 6

[[:Cww]]

It sounds like you have security software running that is trying to keep your system in a certain state.  We've seen this issue in the past with Antivirus companies treating any changes as potentially caused by malware and reverting them when you start your computer.

Comment 7

[GµårÐïåñ]

(In reply to [:Cww] from comment #6)

Normally I would be open that possibility but I know my system and have had it configured a certain way for a long time. I don't use any software or av/malware protection that maintains or contains or edits system state. As I said before, this has never been an issue with the countless and frankly unsettling rate of leveling up in Fx and consecutive updates, it has never affected the profiles in any way. This is the first time and isolated to the 8.0 update. I had the same problem with the 8.x update on another machine and it was no where near as complex or stable of a system as the one I am on, it was pretty much out of the box state on that machine which is used for testing, so we keep it in a state that we can just wipe, throw back the image and move on. It did it on that machine too, so I think its something to do with the way that 8.x installs and "checks" and "manages" the extensions that is causing something. It is just way out of the normal behavior to be a coincidence. But simply put, there is nothing on this machine that would do what you are suggesting, so it still remains, why is it doing this?

Comment 8

[Scoobidiver (away)]

The crash issue is a dupe of bug 691271.
For other issues, file new bugs.