Bug 1440434

The same high CPU usage happens in the demo:

cd /usr/share/doc/wxPython-docs/demo/
python run.py Calendar.py
--> click on button

(In reply to markusN from comment #1)
> The same high CPU usage happens in the demo:
> 
> cd /usr/share/doc/wxPython-docs/demo/
> python run.py Calendar.py
> --> click on button

Using "strace", I see tons of those lines after clicking a button in the demo:

cd /usr/share/doc/wxPython-docs/demo/ ; strace python Calendar.py
...
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\212\10\t\0\1\\!\3\25\1 \3]} \3\362_!\3\0\0\0\0\0\0\0\0\0\0\0\0"..., iov_len=16384}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 16384
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="5 \4\0\335`!\3\333`!\3\260\0 \0\212\4\6\0\336`!\3\335`!\3&\0\0\0"..., iov_len=16384}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 16384
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLIN|POLLOUT}])
recvmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="A\0\365\250q^!\3\3\0\202\0\10\1 \3\0\30\7\0\0\0\0\0\0\0\0\0\0\0\0\0", iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 32
writev(3, [{iov_base="\212\7\2\0\301a!\0036`\2\0\300a!\3>\4\7\0\323`!\3\321`!\3 \1 \3"..., iov_len=16100}, {iov_base="\0\0\240\0\0<\240\0\0\0\343\0\0\0\240\0\0\325\341\0\0<\240\0\0\0\217\1\0\0\240\0"..., iov_len=1120}, {iov_base="", iov_len=0}], 3) = 17220
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\212\27\30\0\3a!\3\262\7 \3j\\!\3\0\0\0\0\24\1 \3\361\0\265\0\1\0\0\0"..., iov_len=16380}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 16380
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\212\10\t\0\10a!\3\240c!\3\0\0\0\0\355b!\3\0\0\0\0\0\0\0\0\0\0\0\0"..., iov_len=16356}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 16356
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\212\10\t\0\10a!\3\\d!\3\0\0\0\0\217b!\3\0\0\0\0\0\0\0\0\0\0\0\0"..., iov_len=4692}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 4692
poll([{fd=3, events=POLLIN}], 1, -1)    = 1 ([{fd=3, revents=POLLIN}])
...

I don't think the problem with the Calendar demo is the same problem.  It could be, but I don't think it is at the moment.

Can you help me figure out how I can run the g.gui under gdb?  If you can figure out the actual python program that it runs, that would be helpful.  I think I've had this same problem before when trying to look into these types of problems.  :-)

Below the answer from grass-dev where I asked for support.
I hope it helps for debugging.

---------- Forwarded message ----------
From: Vaclav Petras
Date: Tue, Apr 25, 2017 at 4:36 PM
Subject: Re: [GRASS-dev] wxGUI unusual high CPU usage debugging
To: Markus Neteler <neteler>
Cc: GRASS developers list <grass-dev.org>

It runs wxgui.py [1], so you can use something like:

cd grass/src
python gui/wxpython/wxgui.py

or:

python $GISBASE/gui/wxpython/wxgui.py

Well, but that's just how to run the Python code directly.

Vaclav

[1] https://trac.osgeo.org/grass/browser/grass/trunk/general/g.gui/main.c#L106

Thank you.  Running gdb wasn't as helpful as I was expecting.  However, it appears that upstream's 3.0 branch doesn't have this problem so it should be possible to fix it.  That also means that F26 probably isn't affected as that's got a relatively recent git snapshot (and a 3.0.3 release is coming soon).

For the record:

As per Bug #1411165 comment 7 the CPU problem is gone with wxGTK3-3.0.3-0.8.gite4293e9.fc25.x86_64.rpm from the COPR test compilation.

(In reply to markusN from comment #6)
> For the record:
> 
> As per Bug #1411165 comment 7 the CPU problem is gone with
> wxGTK3-3.0.3-0.8.gite4293e9.fc25.x86_64.rpm from the COPR test compilation.

Thanks! 3.0.3 was just released, so we can push this to F25.

Update submitted for F25:
https://bodhi.fedoraproject.org/updates/FEDORA-2017-901ccd6490

Hi markusN,

3.0.3 has been pushed to f25. Can you confirm if this issue is fixed?

(In reply to Jeremy Newton from comment #9)
> 3.0.3 has been pushed to f25. Can you confirm if this issue is fixed?

Yes, it is fixed. Thanks!