Out of curiosity, how much hard disk space do you have free?
It's totally possible that the crash reports aren't completely accurate, but here's where I'm getting the numbers.
For this crash, it says that you have about 1GB of physical RAM free, and 500MB of virtual RAM. I don't really understand why the virtual memory pool is so heavily used in this scenario, but it looks like the machine has swapped ~4.2GB of RAM to disk. Virtual Memory is bad -- it means that the operating system is faking additional available RAM by writing to your hard disk, hard disks are on the order of 100,000x slower than doing the same operation in physical RAM, so it's definitely not the first choice.
When I looked at Available Physical Memory, I saw pretty consistently that you had ~1.2 GB free, so I figured it was a system with 2GB of RAM. Either your Firefox instance is eating up ~4GB doing whatever it is that you're doing in a handful of tabs, or you've got other applications running on the system that are competing heavily for available RAM.
The reason that I was thinking 32-bit is laid out a little more clearly here.
On a 64-bit system with a large hard disk and plenty of RAM, you can allocate up to 16TB of RAM for a process, vs. ~2GB on a 32-bit system, or a 64-bit system running a 32-bit Firefox (up until recently, you had to jump through hoops to get 64-bit Firefox, so this was the typical configuration).
Chat Question: Memory Limits for 32-bit and 64-bit processes – ASP.NET Debugging
I also noticed on my second look that the call to js::AutoEnterOOMUnsafeRegion::crash, which makes me think that rather than being a true out of memory condition, this is a case where the JavaScript virtual machine flagged a request for memory allocation as unsafe and aborted. We do something similar in Flash Player, so this may actually be a security thing that's either keeping you safe from an exploit against JavaScript, or it's just a little over-enthusiastic and catching legitimate content. I'm just making an educated guess. Someone that actually works on Firefox could probably offer more insight into what's going on here.
| OOM | unknown | js::AutoEnterOOMUnsafeRegion::crash | JS::Zone::adoptUniqueIds |
| Total Virtual Memory | 4,294,836,224 bytes (4 GB) |
|---|
| Available Virtual Memory | 499,023,872 bytes (475.91 MB) |
|---|
| Available Page File | 6,242,570,240 bytes (5.81 GB) |
|---|
| Available Physical Memory | 1,053,831,168 bytes (1005.01 MB) |
|---|
It's a very low-volume crash, doesn't involve Flash, and seems to be distributed appropriately across multiple versions of Firefox, such that probably isn't something that was caused by the latest update.
OOM | unknown | js::AutoEnterOOMUnsafeRegion::crash | JS::Zone::adoptUniqueIds - Signature report - ...
For this one:
[@ OOM | small] - Firefox 49.0.1 Crash Report - Report ID: f2567763-04c0-456f-80e9-c82eb2161021
| Total Virtual Memory | 4,294,836,224 bytes (4 GB) |
|---|
| Available Virtual Memory | 166,780,928 bytes (159.05 MB) |
|---|
| Available Page File | 6,093,422,592 bytes (5.67 GB) |
|---|
| Available Physical Memory | 1,281,617,920 bytes (1.19 GB) |
|---|
| System Memory Use Percentage | 79 |
|---|
| OOM Allocation Size | 1,044 bytes (1.02 KB) |
|---|
Again, you have a really small available virtual memory pool (~160MB), and a lot of physical RAM, but Firefox attempted to allocate 1.02K of memory and wasn't able to, so it crashed.
This is a high-volume crash, but one that you'd expect to see through normal usage by a large volume of users:
OOM | small - Signature report - Mozilla Crash Reports
In both instances the disk-based Virtual Memory pool is heavily used, which indicates that the physical RAM is unavailable. It may be that this is simply a bad case of memory fragmentation (see Internal Fragmentation here: Fragmentation (computing) - Wikipedia ) such that while there are free blocks of memory, they're not in a contiguous, usable distribution.
It's interesting to me that the System Memory Use Percentage and OOM Allocation Size rows are only present in this crash, which supports my theory that the first one wasn't a true OOM condition, but simply leverages the same facilities to punch out in a safe way when memory allocations start failing.
I don't see anything that would change my guidance really. You're running out of usable memory. It might be that a different browser would do a more efficient job in handling and compacting memory allocations such that more of that remaining 1.2GB of RAM would stay in a usable configuration. I'm guessing that you don't have a ton of free disk space.
17
Replies
but as Once the page reloads, as soon as I click on something or just wait for a while, Adobe Flash crashes. 
Make sure when u install the following firefox addon you set shockwave flash to never activate in firefox addon settings. I hope this helps. 
AdChoices