Closed Bug 532798 Opened 16 years ago Closed 9 years ago

Startup crash in [@ SEPsearchhelperff.dll@0xd7c5 ]

Categories

(Firefox :: Extension Compatibility, defect)

x86
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: marcia, Unassigned)

References

Details

(Keywords: crash, Whiteboard: [crashkill])

Crash Data

Seen while trying to start up the trunk build on Windows 7. http://tinyurl.com/yhyhl27 is the link to all the crashes on the trunk. The crash comments indicate that the MSN toolbar had recently been installed. STR: 1. Have side by side installs of Trunk, B4, Namoroka but all use their own profiles 2. I installed the MSN toolbar in Beta 4. 3. I tried to start up the trunk with my existing profile and I crash 100% on startup. I then tried a new profile and the same thing happened. Currently in this state I cannot start up my trunk build at all without crashing.
Blocks: 532832
sounds like the crashing plugin gets installed in c:\program files\microsoft\search enhancement pack\search helper\firefoxextension\searchhelperextension\components\SEPsearchhelperff.dll see if you find it there. If you can you might try removing that file and see of the trunk build starts. Is there any incompatiblity and inability to start on b4 or other releases or is it just trunk? Looks like there are several problems with that .dll and we will need to get a contact at microsoft.
SEPsearchhelperff.dll 2.0.264.0 appears to be the version of the .dll assoicated with this problem
Component: General → Extension Compatibility
QA Contact: general → extension.compatibility
The plugin in Comment 2 is present on the machine that was crashing, but now I am not having problems crashing. I went to trunk right away since the lone comment was from someone running on trunk. Will try on B4 or the Namoroka nightlies and report back.
Crash Signature: [@ SEPsearchhelperff.dll@0xd7c5 ]
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.