Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 3 subscribers
  • Views 3994 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Incompatbile to multi process from firefox?

Fabian H

Since ~ one month I have frequent crashes of firefox.

So I just decided to ask at firefox support and they told me that it is a problem of Sophos:
https://support.mozilla.org/t5/Firefox/Firefox-Crashes-Random-freeze-crash-when-switching-tab-up-to-5/m-p/1388306#M1045997

So is it? And what to do to make Sophos fix this problem ?



This thread was automatically locked due to age.
Parents
  • 0

    You would need to supply support with a full dump of firefox.exe when it crashes.

    I would suggest to get procdump.exe - https://technet.microsoft.com/en-gb/sysinternals/dd996900.aspx.

    In a admin command prompt with procdump.exe in the path, run:

    mkdir C:\dumps
    procdump -ma -i c:\dumps

    Reproduce the issue and you should get a full dump of Firefox in the dumps directory.  I would zip and send this to Support with an SDU file (community.sophos.com/.../33533).

    Once done, you can uninstall Procdump as the default debugger running:

    procdump -u

    It might be worth getting a few dumps (and SDU logs) even from different computers if you have them to prove it's the same issue.

    Regards,

    Jak

Reply
  • 0

    You would need to supply support with a full dump of firefox.exe when it crashes.

    I would suggest to get procdump.exe - https://technet.microsoft.com/en-gb/sysinternals/dd996900.aspx.

    In a admin command prompt with procdump.exe in the path, run:

    mkdir C:\dumps
    procdump -ma -i c:\dumps

    Reproduce the issue and you should get a full dump of Firefox in the dumps directory.  I would zip and send this to Support with an SDU file (community.sophos.com/.../33533).

    Once done, you can uninstall Procdump as the default debugger running:

    procdump -u

    It might be worth getting a few dumps (and SDU logs) even from different computers if you have them to prove it's the same issue.

    Regards,

    Jak

Children
No Data
Unfiltered HTML