Freezes

[homer]

Recently I started having problems with my SEQ freezing... it starts taking up 99.9% of the CPU's time and such. It has only been happening in certain zones, OT, FM, WW, for example.. SOmetimes shutting it down and restarting it fixes it. But I am NOT sure what is going on.. somes times when it receives the key, it will fix itself.

[Cryonic]

What version of QT?

[homer]

Actually running RedHat 8.0, so what ever version was compiled in it when I installed it.

[permafrost]

Red Hat 8.0 comes with QT 3.0.x. I think its 3.0.5. There are known issues with that version of QT.

I recommend you downlaod QT 2.3.x source and install it. Don't try the RPMs, that will cause conflicts with existing RPMs.

There are links to it in several threads that you could easily find using the search feature.


permafrost

[Jel321]

Ive actually had the same problem lately running run Redhat 7.2 and the QT's pulled from Zaphods pre-compiled stuff.

Never really totally locks up but gets to the point where its a good 10-20 secs between performing an action and seeing SEQ respond.

[datadog]

Well,

Here is the thread (http://seq.sourceforge.net/showthread.php?s=&threadid=2510&highlight=qt2.3.2) from my qt-2.3.2 in RH 8 experience.

Maybe it will help you. YMMV!

[Dedpoet]

I will just confirm that QT 3.0.x just didn't run well with Seq for me. There are plenty of people for whom it is working just fine, but I think all of us using Gentoo have gone back to 2.3.2, and I have seen several posts about this topic in other distros as well. Personally I had freezes, font issues, map update problems, map lines disappearing, and just generally bad performance with 3.0.5. Going back to 2.3.2 fixed everything for me.

[BadgerOne]

try resizing the showeq window. I always have a CPU/MEM usage display in the panel, when I CPU usage is at 99%, I start resizing the window until the CPU Usage drops back. It stays low then until I zone.

[homer]

Ok, wiping it out and then installing QT 2.3.2 and recompiling SEQ worked.

Thanks for all the info guys.

[joojooga]

Yup. Dropping down to 2.3.2 fixed it all. I had the exact same problem. Zones decode within 2 seconds every time. And latest CVS seems to really run faster.

[Sodom]

I'm glad I'm not the only having this issue, will give the QT fix a try tonight. Strange how it just started happening all of a sudden.

[joojooga]

Additional information - You'll find that it's just easier to FTP straight into trolltech and grab 2.3.2 than search around forever on their website. Additionally, when you compile it, be sure to use the -thread option.


Lastly, grab the latest CVS since you're doing this anyway...it's really good.

[Yueh]

------------------ And Four Months Pass ...................................


I hate to dredge this back up but the new and improved SEQ is causing this same problem for me for the first time. I'm running Gentoo with QT 3.1.2. Ran SEQ for years no problem but now, with the latest SEQ and Gentoo I'm having the same resource issue again. Resizing the window helps, takes CPU utilization of X from 99.9% to about 50-60% but it is still obviously borked. Is anyone else seeing this and if so, have you managed to resolve it?

I'm updating to QT 3.1.2-r3 just for kicks to see if that helps but I'm not holding my breath. I think downgrading to QT 2.3 at this point is probably not an option for SEQ correct?

[Zeppo]

Right.
SEQ now requires qt3.

I am using qt-3.1.1 with no problems on a RH 7.2 system.