搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

Firefox 5.0 and 7.0.1 crash or disappear after upgrading from Frontmotion

  • 4 个回答
  • 2 人有此问题
  • 5 次查看
  • 最后回复者为 onedrum

more options

We've been using Frontmotion 3.5.5 for too many years, and we're working to push an update to Firefox using SCCM. However, we've run into a bit of a show stopper.

We uninstalled Frontmotion 3.5.5, then installed Firefox 5.0 and customized it using a CFG file (not encrypted). The behavior we're seeing is that it opens, and a few seconds later it closes; no error, no entry in event viewer, no crash report from about:crashes. It opens fine in safe mode, but even if we disable everything we can find, it won't run outside of safe mode. Sometimes, it will actually work fine for up to maybe an hour or two, but then it either disappears like that or crashes, generating an application event log entry.

We pushed Firefox 7.0.1 instead, then, hoping that it was a known issue that had been fixed, but 7.0.1 is doing the same thing. This is happening on 3 of the 7 machines we've pushed to so far.

We use roaming profiles, and so far the problem seems to be related to something on the machine rather than the profile; a local profile has the same behavior and users with the problem seem to be able to work fine on other computers with FF7 installed. I've actually gone as far as utilizing Windbg to try to isolate the culprit, but I haven't had a lot of success.

Can anyone help, perhaps?

We've been using Frontmotion 3.5.5 for too many years, and we're working to push an update to Firefox using SCCM. However, we've run into a bit of a show stopper. We uninstalled Frontmotion 3.5.5, then installed Firefox 5.0 and customized it using a CFG file (not encrypted). The behavior we're seeing is that it opens, and a few seconds later it closes; no error, no entry in event viewer, no crash report from about:crashes. It opens fine in safe mode, but even if we disable everything we can find, it won't run outside of safe mode. Sometimes, it will actually work fine for up to maybe an hour or two, but then it either disappears like that or crashes, generating an application event log entry. We pushed Firefox 7.0.1 instead, then, hoping that it was a known issue that had been fixed, but 7.0.1 is doing the same thing. This is happening on 3 of the 7 machines we've pushed to so far. We use roaming profiles, and so far the problem seems to be related to something on the machine rather than the profile; a local profile has the same behavior and users with the problem seem to be able to work fine on other computers with FF7 installed. I've actually gone as far as utilizing Windbg to try to isolate the culprit, but I haven't had a lot of success. Can anyone help, perhaps?

所有回复 (4)

more options

Your best bet is to capture a stacktrace -> https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report

If you can come up with a stacktrace and reliable steps to reproduce, open up a bug report.

more options

That's part of our problem I guess: we can't really reproduce on demand. Sometimes it works just fine for an hour and a half and then suddenly it will crash and die, or just disappear with no error or anything. If it always exited immediately or crashed after being opened, then at least we could test possible solutions relatively quickly, but no.

I have stacktraces but not steps to reproduce. Is it worth creating a bug report if I can't provide those steps?

more options

You can try - cc me on the bug (fmdevelopertim@gmail.com) and I will get someone to take a look at it who knows more about stacks than me.

more options

I opened bug 697129 yesterday:

https://bugzilla.mozilla.org/show_bug.cgi?id=697129

I remember there was a list of recipients when I opened it, but I don't see a place where I can add someone now. Hopefully, the link above provides enough information to run with it.

I really appreciate your help! Thanks!