Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

How to fix 1-2second freezing, high memory usage, and just now Crashing?

  • 1 reply
  • 1 has this problem
  • 3 views
  • Last reply by John99

more options

Recently, I have found Firefox to be "freezing" or "choppyness" where the whole browser will stop for a second or two before continuing off again. Let's say that I was typing something, I would experience a frozen browser but if I'm still typing during the freeze, after the freeze what I had typed would appear. And when I'm watching a youtube or facebook video, the clips would freeze and and there would be small 1-3 second interruptions in video and sound. This has been getting on my nerves and seems apparent after the new update. This is happen on both of my laptops which have firefox, one being a 2011 laptop and the other a 2014 laptop.

Also, I have noticed that Firefox would use up a lot of memory and jumping over 1,000MB of memory. This can cause Firefox to go very slowly in comparison to Chrome which doesn't experience that type of behavior. Additionally, I ran across two crashes just today: bp-c08a1d33-0301-49a3-85c3-ad1d82150801 bp-ca07ce0e-4aa3-4ed7-800d-c80592150801

In both crashes I have gotten this message: The exception Breakpoint A breakpoint has been reached. (0x80000003) occurred in the application at 0x748e1aa1

Recently, I have found Firefox to be "freezing" or "choppyness" where the whole browser will stop for a second or two before continuing off again. Let's say that I was typing something, I would experience a frozen browser but if I'm still typing during the freeze, after the freeze what I had typed would appear. And when I'm watching a youtube or facebook video, the clips would freeze and and there would be small 1-3 second interruptions in video and sound. This has been getting on my nerves and seems apparent after the new update. This is happen on both of my laptops which have firefox, one being a 2011 laptop and the other a 2014 laptop. Also, I have noticed that Firefox would use up a lot of memory and jumping over 1,000MB of memory. This can cause Firefox to go very slowly in comparison to Chrome which doesn't experience that type of behavior. Additionally, I ran across two crashes just today: bp-c08a1d33-0301-49a3-85c3-ad1d82150801 bp-ca07ce0e-4aa3-4ed7-800d-c80592150801 In both crashes I have gotten this message: The exception Breakpoint A breakpoint has been reached. (0x80000003) occurred in the application at 0x748e1aa1

All Replies (1)

more options

These issues can be difficult to investigate. 1000MB may not be much with multiple tabs open and video in use. The memory usage may not be the problem. The crash reports both show less than 50% memory usage so possibly memory usage is not directly involved with the crash or any slowness. It may be of interest to see how Google Chrome compares for memory use in similar situations. (But Google Chrome may be better at handling memory in that sort of situation).

YouTube probably uses HTML5 on Firefox. I presume facebook will use Flashplayer. For Flashplayer problem have a look at

It may be worth trouble shooting by turning off hardware accelertion. That may actually make Firefox slower, but if it helps then you should investigate further & check whether updating graphics drivers helps the problems.

As for the crash possibly not worth investigating, at the moment unless they occur on a regular basis. if we do need to investigate then the first step will be to test Firefox in its safe mode and see if the crashes still occur.


For forum cross referencing purposes

  • Reports for your Crash IDs
    bp-c08a1d33-0301-49a3-85c3-ad1d82150801
    bp-ca07ce0e-4aa3-4ed7-800d-c80592150801
  • Crash Signature: js::detail::HashTable<T>::lookupForAdd(char const* const&)
  • Related bug: Bug 1189934 - crash in js::detail::HashTable<T>::lookupForAdd(char const* const&)
  • My Comments: Crashing threads involve cfgmgr32.dll or rtworkq.dll
    This is not a common crash signature.