<![CDATA[Opera burns CPU with poll()+recvmsg() loop]]>Opera 45.0.2552.812, latest Arch Linux.

Right from start Opera burns CPU with poll() loop as shown by strace: [1]

It is always 2 file descriptors, in this case, 110 and 117.

Looking at it closer, strace shows backtraces for each EAGAIN'ed recvmsg: [2]

Looks like it has something to do with X server interaction.

Checking those descriptors here: [3]

Closing those descriptors via gdb results in Opera SIGSEGV.

Always reproducible, even with clean profile and no extensions.

Is there any option how to save my CPU cycles?

Thanks.

[1] https://gist.github.com/a8d11ac5477982128525f51f11d3ca4d
[2] https://gist.github.com/d32b99483a5c236cbd92aa38e586741f
[3] https://gist.github.com/5aee3ef7d487a67e23d7d001f2c46ea6

]]>https://forums.opera.com/topic/20901/opera-burns-cpu-with-poll-recvmsg-loopRSS for NodeThu, 11 Jun 2026 12:01:37 GMTSat, 20 May 2017 23:48:17 GMT60<![CDATA[Reply to Opera burns CPU with poll()+recvmsg() loop on Fri, 07 Jul 2017 09:17:30 GMT]]>Same with v46.0.2597.39.

]]>https://forums.opera.com/post/124456https://forums.opera.com/post/124456Fri, 07 Jul 2017 09:17:30 GMT<![CDATA[Reply to Opera burns CPU with poll()+recvmsg() loop on Wed, 28 Jun 2017 12:17:47 GMT]]>Still applies to v46.0.2597.32.

]]>https://forums.opera.com/post/124011https://forums.opera.com/post/124011Wed, 28 Jun 2017 12:17:47 GMT<![CDATA[Reply to Opera burns CPU with poll()+recvmsg() loop on Fri, 23 Jun 2017 05:09:16 GMT]]>@avl, in Task Manager, "Browser" process consumes 15 to 25% of CPU.

Still applies to v46.0.2597.26.

]]>https://forums.opera.com/post/123756https://forums.opera.com/post/123756Fri, 23 Jun 2017 05:09:16 GMT<![CDATA[Reply to Opera burns CPU with poll()+recvmsg() loop on Thu, 22 Jun 2017 13:07:19 GMT]]>Hi @pfactum, what you're seeing in strace is the message loop. Every UI application has one, and among other things, it handles communication with the X11 server. It is indeed very busy - a browser sends and receives lots of messages, many in one second. Getting EAGAIN is a normal part of life, and might indicate that Opera is busy (meaning that messages that are no longer relevant don't need to be handled). The EAGAIN is more likely to be a symptom than an effect of the high CPU usage you see.

If you still see high CPU usage while using Opera, check out the built-in Task Manager to see exactly which process is using CPU, perhaps then we can find out what's happening on your system.

]]>https://forums.opera.com/post/123729https://forums.opera.com/post/123729Thu, 22 Jun 2017 13:07:19 GMT<![CDATA[Reply to Opera burns CPU with poll()+recvmsg() loop on Wed, 14 Jun 2017 08:13:20 GMT]]>Same with v45.0.2552.898.

]]>https://forums.opera.com/post/123335https://forums.opera.com/post/123335Wed, 14 Jun 2017 08:13:20 GMT<![CDATA[Reply to Opera burns CPU with poll()+recvmsg() loop on Wed, 07 Jun 2017 06:00:48 GMT]]>Again, same applies to Chromium 59.0.3071.86, but to less extent. strace shows the same picture, but recvmsg fails with EAGAIN once per several seconds, thus CPU load is minimal. For Opera, recvmsg returns EAGAIN lots of times per second, and CPU load is noticeable.

So, this has something to do with common engine code, likely, interaction with X server.

]]>https://forums.opera.com/post/122976https://forums.opera.com/post/122976Wed, 07 Jun 2017 06:00:48 GMT<![CDATA[Reply to Opera burns CPU with poll()+recvmsg() loop on Tue, 06 Jun 2017 12:20:44 GMT]]>Having nothing to add to your problem, I would like to mention that chromium was updated to 59.x today from upstream. Check if that solves your problem.

]]>https://forums.opera.com/post/122924https://forums.opera.com/post/122924Tue, 06 Jun 2017 12:20:44 GMT<![CDATA[Reply to Opera burns CPU with poll()+recvmsg() loop on Tue, 06 Jun 2017 12:13:23 GMT]]>Same with 45.0.2552.888.

]]>https://forums.opera.com/post/122923https://forums.opera.com/post/122923Tue, 06 Jun 2017 12:13:23 GMT<![CDATA[Reply to Opera burns CPU with poll()+recvmsg() loop on Sun, 28 May 2017 17:56:40 GMT]]>Same applies to 45.0.2552.881.

]]>https://forums.opera.com/post/122186https://forums.opera.com/post/122186Sun, 28 May 2017 17:56:40 GMT<![CDATA[Reply to Opera burns CPU with poll()+recvmsg() loop on Mon, 22 May 2017 17:05:46 GMT]]>Same applies to Chromium 58.0.3029.110. The only difference is that EAGAIN arrives more rarely (once per several, up to 10, seconds), thus CPU is not used that high as by Opera.

So, it has something to do with engine.

]]>https://forums.opera.com/post/121570https://forums.opera.com/post/121570Mon, 22 May 2017 17:05:46 GMT<![CDATA[Reply to Opera burns CPU with poll()+recvmsg() loop on Mon, 22 May 2017 10:47:03 GMT]]>Reproduced on 2 machines with Arch and on 1 machine with Gentoo. CPU usage varies depending on CPU power, but strace shows similar picture (EAGAIN flood).

]]>https://forums.opera.com/post/121502https://forums.opera.com/post/121502Mon, 22 May 2017 10:47:03 GMT