Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

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

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

When I search the *new* Google Images, Firefox suffers a memory overload

  • 1 eyano
  • 25 eza na bankokoso oyo
  • 1 view
  • Eyano yasuka ya androidlove

bauhsoj
bauhsoj
more options

When I search using the *new* Google Images that loads image thumbnails dynamically as I scroll, Firefox suffers a memory overload.

What I have noticed by checking the Windows Task Manager is that each time a tab is opened to a Google Images search Firefox's memory usage increases by about 20 MB. When that tab is closed, the memory usage only goes back down by about 1 MB. Eventually the browser reaches the system's capacity to handle it (about 1.3 GB in my case) and Firefox must then be forcefully terminated.

Although it might seem a simple solution is to just not open so many Google Image searches, my job depends on my ability to use it to research every image I am given daily (100's).

What could be causing this, and better yet, how can I stop it from happening?

When I search using the *new* Google Images that loads image thumbnails dynamically as I scroll, Firefox suffers a memory overload. What I have noticed by checking the Windows Task Manager is that each time a tab is opened to a Google Images search Firefox's memory usage increases by about 20 MB. When that tab is closed, the memory usage only goes back down by about 1 MB. Eventually the browser reaches the system's capacity to handle it (about 1.3 GB in my case) and Firefox must then be forcefully terminated. Although it might seem a simple solution is to just not open so many Google Image searches, my job depends on my ability to use it to research every image I am given daily (100's). What could be causing this, and better yet, how can I stop it from happening?

All Replies (1)

androidlove
androidlove
more options

I also have the same problem. It might be causing the images not to load. Firefox sits there waiting. If I refresh, I get a few more images.