app using "excessive" CPU

mzimmers

@SGaist not explicitly. I do this:

    qhv->setSectionResizeMode(QHeaderView::Stretch);

But disabling that line doesn't reduce CPU noticably.

JonB

@mzimmers
Sit down, grab a coffee & a pack of cigs. Start binary-chopping-commenting-out half your code at a time. It can't be that hard to get to the point where these update requests do not happen... :) For example, first get rid of all hidden columns. Then reduce to fewer columns than the width of the window. With 2 rows. Then no rows and no columns --- does it still happen then?!

What are you using which gives you those events printed out?

mzimmers

@JonB OK, I'll belly up to removing the hidden rows (I was hoping to avoid that).

I've already sized my widget so that everything is fully displayed.

I even disconnected the signal that tells the model to update. My tableView is completely empty. And I'm still getting the CPU usage.

Here's what I use to show me the events:

bool KeyPress::eventFilter(QObject *obj, QEvent *ev)
{
    bool rc = false;
    QEvent::Type type;
    static int count = 0;

    type = ev->type();
    qDebug() << count++ << QTime::currentTime().toString() << type;

    rc = QObject::eventFilter(obj, ev);
    return rc;
}

It may be noteworthy that disabling this filter entirely doesn't help.

mrjj

Hi
Could you not add a paintEvent handler where you simply call base class but
then add a break point and that way maybe see how its triggered ?

JonB

@mzimmers said in app using "excessive" CPU:

My tableView is completely empty. And I'm still getting the CPU usage.

Which is the sort of thing which is interesting, so you don't want to waste time looking at resizes. Nonetheless, the events indicate widget updating?

I had forgotten about your KeyPress and its eventFilter. Get rid of it completely from your code! You don't want to be messing about with your key press stuff from your other thread. Now what's the speed? It ought be still slow, but you never know.

Then get rid of all your own "event filters". Reintroduce only one at the very top level to debug monitor whatever you need to.

mzimmers

@mrjj I can do something like this:

void Widget::paintEvent(QPaintEvent *event)
{
    QWidget::paintEvent(event);
}

But I don't know what kind of meaningful information I can extract from the event argument. (According to the docs, paintEvent() isn't a slot.)

mzimmers

@JonB I've gotten rid of all filters, all hidden columns, and have disconnect model updates after I create two rows. I also disabled stretch mode, and expanding policy. Still using 11% CPU.

This might be a good time to point out that I "stole" the code for this app from another project, which doesn't have this problem. For the life of me, I can't see what I added that causes this.

JonB

@mzimmers
Try not running your application, or switch the machine off ;-)

Given that this is running on Windows, I can't use the profiler built into Creator

Does your MSVC/MinGW compiler come with a usable profiler, nothing to do with Qt?

In your paintEvent() override @mrjj had in mind for you to try a debugger breakpoint there and look at the stack trace. You will doubtless need to perhaps put a delay/count on the breakpoint, or set it while the app is in the middle of running. I don't actually know whether paint events will show anything interesting on the stack.

You can use the top-level eventFilter() to examine most of what's going on, if you have to :( Debug every event's type to file/debug output window for a couple of seconds into your "idle". Search the output, you're probably interested in what you see just before the updating starts, or as it goes along.

mzimmers

@JonB using MinGW, and I don't think it has a profiler. I could look at 3rd party products, but it's probably easier just to have a co-worker build this on Linux, and then run the profiler. (Hopefully the problem will occur on Linux!)

Here's the stack trace you mentioned:

Maybe you can see something useful in it; I can't.

JonB

@mzimmers
An expert may have something to say about the traceback. All I know is it would be nice to know which the QWidget is. Wait, this code is yours for Widget? So which of your widgets is it? If you break more than once, is it always the same widget?

I can see QCoreApplication::sendSpontaneousEvent(). You sure you're not "wiggling"? :)

(Hopefully the problem will occur on Linux!)

Nope... ;-)

mzimmers

@JonB yes Widget is my oh-so-creative name for my main QWidget class, which is the only QWidget the app uses (unless you push one of the buttons). So yeah, it's always the same Widget.

Someone else mentioned wiggling, but I'm not sure I know what it means. The problem occurs even when the app loses focus, though.

And, if you're confident this won't happen on Linux, then maybe the problem isn't in my code space...

JonB

@mzimmers said in app using "excessive" CPU:

And, if you're confident this won't happen on Linux, then maybe the problem isn't in my code space...

Noooo, I put a wink --> ;-) <--
I absolutely do not know whether it will repro under Linux, if you're lucky it will, I just meant sod's law it won't!

mrjj

@mzimmers
Hi
That stack trace is for

starting app
2: add break point
3: let it loose focus to see the issue

and not just set at startup so we ssee the first paint when it becomes visible?
Just asking to be sure. Not seeing anything special besides maybe the sendSpontaneousEvent

mzimmers

@mrjj I'm not sure I follow you, but I modified my routine:

void Widget::paintEvent(QPaintEvent *event)
{
    static int count = 0;
    if (event->spontaneous())
    {
        //qDebug() << "spontaneous event" << count++;
    }
    else
    {
        QWidget::paintEvent(event);
    }
}

I put a breakpoint on QWidget::paintEvent...and it never, EVER hits. (Also, with this change, CPU usage remains the same.)

This just gets weirder and weirder.

fcarney

I am sorry this is such a struggle. I don't have anything more to add except a sarcastic example of wiggling:
https://media.giphy.com/media/xT9KVjBI3W2283URdm/source.mp4

mrjj

@fcarney
hehe that the sorts you want to debug with a flame thrower...

mrjj

@mzimmers

well i just asked if it was not as in first run stack trace.
but i think you are doing as i think reading your last post.

Its very odd. Indeed.
Does
//qDebug() << "spontaneous event" << count++;
trigger alow when testing then ?

mzimmers

@mrjj I just realized something -- from the docs:

bool QEvent::spontaneous() const
Returns true if the event originated outside the application (a system event); otherwise returns false.

The return value of this function is not defined for paint events.

So, I think this exercise was a waste of time.

mrjj

@mzimmers

Well i find it very odd you see many paint events for the widget (with event filter) but
its not constantly Hitting the break point in paintEvent. ??
Or did i misunderstood something ?

mzimmers

@mrjj you understand it perfectly, and "odd" is a mild term for it.

I seriously don't know what to look at here. I'm afraid that the profiler we run tomorrow won't show anything in my code space.