Thu 19 Aug 2010 07:05:13 PM UTC, comment #11:
Compiling against Ruby 1.8.7 fixes the issue. No luck with 1.9.2.
|
Thu 19 Aug 2010 05:50:51 PM UTC, comment #10:
Interesting, an idle irb session gives me 98 wakeups/sec. I also found this thread:
http://www.ruby-forum.com/topic/200147
Seems like it is a problem with threading in 1.9. Hopefully 1.9.2 fixes, but I'm going to wait until there's a package to install.
Thanks again. I vote for closing this.
|
Thu 19 Aug 2010 03:48:34 PM UTC, comment #9:
OK, it may take me a bit to get it set up with 1.8, but I'll post here if that works.
Also, just fyi I see 1.9.1 support mentioned here:
http://www.weechat.org/files/changelog/ChangeLog-0.3.1.1.html
Also 1.9.1 is apparently supposed to be stable:
http://www.ruby-lang.org/en/news/2009/01/30/ruby-1-9-1-released/
Thanks for the help. I don't mind unloading the ruby support for now as I'm not using it. I'll try to test with 1.8 and/or poke around in the source (though I probably won't be much help) if I get a chance, but feel free to close the bug if need be.
|
Thu 19 Aug 2010 03:05:52 PM UTC, comment #8:
I'm not sure WeeChat can work with ruby 1.9.
By the way, I think this version (1.9.1) is considered as "unstable". You should only link with ruby 1.8 for WeeChat today.
When I'll have some time, I'll test WeeChat with ruby 1.9.2. Or if someone feels able to do it, patches are welcome :)
If everything is ok with ruby 1.8, I'll close this bug.
Feel free to open another bug for ruby 1.9 support.
|
Thu 19 Aug 2010 02:53:03 PM UTC, comment #7:
Unloading the ruby plugin with all others loaded gets rid of the wakeups. If I try to reload the plugin, weechat crashes. (Running ruby 1.9.1)
|
Thu 19 Aug 2010 02:51:32 PM UTC, comment #6:
Can you try to load plugins one by one? And track which plugin causes so many wakeups.
With command:
/plugin load xxxx
I heard about perl problems recently in archlinux, maybe it's perl plugin? But not sure, please try! :)
|
Thu 19 Aug 2010 02:41:26 PM UTC, comment #5:
Disabling the plugins worked. A copy I just compiled locally has the same symptoms.
|
Thu 19 Aug 2010 02:22:59 PM UTC, comment #4:
Ok, next test is:
weechat-curses --dir /tmp/weechat -p
This will run only core (no plugin/script). Please tell me if you still have 100 wakeups/seconds.
Another thing, can you try to compile WeeChat yourself ?
I never used archlinux, but I know that many users have various problems using their packages, maybe problem is here..
|
Thu 19 Aug 2010 02:16:05 PM UTC, comment #3:
A little more info: the PKGBUILD calls configure using --with-debug=0 LDFLAGS="-lm -ldl"
|
Thu 19 Aug 2010 02:07:27 PM UTC, comment #2:
Yes, it is definitely version 0.3.3 (the current Arch package).
weechat-curses --dir /tmp/weechat -s still gives me 100 wakeups/sec on my netbook. It also gives me 99 wakeups/sec on my desktop box using 0.3.2.
These plugins are still listed as loaded when using the command above:
Plugins loaded: alias, aspell, charset, fifo, irc, logger, lua, perl, python, ruby, tcl, xfert
|
Thu 19 Aug 2010 09:14:21 AM UTC, comment #1:
Are you sure you're testing with 0.3.x version and not with 0.2.x ?
This problem was in all releases before 0.3.0 (ie in 0.2.6.x and older). It has been fixed in 0.3.0.
Please try that:
weechat-curses --dir /tmp/weechat -s
And then look at number of wakeups/sec. Here I have 2.0 wakups/sec, you should have something between 2 and 3 per second (with default config, default plugins, no script loaded).
|
Tue 17 Aug 2010 04:44:24 PM UTC, original submission:
This still happens when running weechat-curses with the --no-script param. irc.network.lag_min_show = 1000. powertop consistently reports 100 wakeups/sec. Pretty much the same as #21985, but that seems to have been marked as fixed quite a while back.
Thanks, big fan of weechat.
|