Do more on the web, with a fast and secure browser!

Download Opera browser with:

  • built-in ad blocker
  • battery saver
  • free VPN
Download Opera
  • hello all
    i have probleme
    Opera running on multiple cpu
    I want to work on sigle cpu
    please help me
    i love opera

  • Opera 12 was the last version of Opera that would run on a single CPU using only a single process. Opera 15 and above splits each tab into its own process, just like other Chromeium based browsers.

  • Is there a solution in the latest version of Opera

  • Is there a solution in the latest version of Opera

    Nope. And all major browser/softwares will go into multiple (cpu) processes sooner or later.

  • Mozilla "Firefox" running single cpu
    but i love Opera
    help me

  • What is your main concern with a single cpu running multiple processes, as in Opera? Older computers do this all the time with multi-tasked architectures, although they do slow down with operation-intensive software. If you want old or simple hardware, you have to sacrifice software features, speed, and complexity; if you want features and speed, you have to upgrade the hardware to accommodate it. There are a number of 'light' browsers out there that will work speedily on older systems (eg: ), but the latest versions of Opera, Chrome, Firefox, and IE are not among them.

  • Mozilla "Firefox" running single cpu

    Currently yes but it may change.

    i love Opera help me

    What exactly is the problem with multiple cpu processes for you? Unless you are running a very old and/or very hardware limited computer, multiple processes will not cause any major issues.

  • Why Mozilla
    Running on a single processor

  • The Mozilla designs are based on single-process operation for the browser. This was an older approach used at one time by all browsers (and all software, since multiple processors didn't exist in those days). Multi-tasking the computer's single processor was used by the software and host computer to run multiple programs at the same time by quickly switching on and off the various individual running programs' access to the CPU core. Unfortunately, with a lot of things running on the computer, a particular program could only receive a limited share of the processor's attention which slowed down the program's operation. Later, by incorporating multiple processors in the hardware, a given program could be given an increased share of a CPU processor's attention and run faster.

    Then, with multiple CPU cores available, software began to be written to take full advantage of the added capabilities inherent with the added CPU cores. At some point, many resource-intensive programs began to heavily rely on the presence of multi-processor architecture to maintain their speedy performance. While many such programs can still operate on single-processor systems, they tend to run slower or require the use of less resource-expensive features by the user in order to maintain a reasonable speed. Beyond that, having each tab and extension running in its own process provides a browser with resistance to total crashing if one tab or extension crashes by itself. Unfortunately, the use of these extra processes requires much more sharing of attention when/if a single-processor CPU is used, hence it tends to slow down such a system's overall operation. Mozilla apparently has elected up until now to maintain their single-process design (which tends to be more optimized for single CPU systems), but there are reports Mozilla will also eventually be moving to a multi-process browser design in the not-so-distant future.

    There is a sometimes-unpleasant reality that as hardware inevitably evolves in capability, software also evolves to where it relies on the advanced hardware. This leaves older systems lacking in the necessary capacity to run newer software as effectively. Unfortunately, it's simply the way things are in the real world.