Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No response! Force quit! #653

Open
gsamful opened this issue Jul 4, 2015 · 18 comments
Open

No response! Force quit! #653

gsamful opened this issue Jul 4, 2015 · 18 comments

Comments

@gsamful
Copy link

gsamful commented Jul 4, 2015

I always receive the message above after logging WebQQ within half an hour. How to fix it?

@xiehuc
Copy link
Owner

xiehuc commented Jul 6, 2015

i don't clear what you are saying

@gsamful
Copy link
Author

gsamful commented Jul 7, 2015

I always receive the message "No response! Force quit! " after logging Web QQ for about 30 minutes! I have to force quit by gnome-system-monitor! Any idea to sovle it? Thank you!

@lainme
Copy link
Contributor

lainme commented Jul 7, 2015

我也遇到了。基本就是登录之后,pidgin没过多久就会停止响应,只能强制关掉。还没确定问题在pidgin还是pidgin-lwqq。因为arch上pidgin最后一次更新是在6.28,这又是这几天刚出现的,估计和这次更新有关。
又看了下,上次更新只是对perl 5.22重新编译了一下……

@gsamful Are you using archlinux with the latest pidgin? I am also facing this problem

@gshmu
Copy link
Collaborator

gshmu commented Jul 7, 2015

要这么说,我的从待机恢复或者挂起恢复时也会,初步判断是网络问题导致pidgin。。。
不知道你们是不是这个原因,电脑网络自动断开什么的 🎱

@gsamful gsamful closed this as completed Jul 7, 2015
@gsamful
Copy link
Author

gsamful commented Jul 7, 2015

Uploading Screenshot from 2015-07-07 16-55-15.png…
Gentoo@lainme

@gsamful gsamful reopened this Jul 7, 2015
@gsamful
Copy link
Author

gsamful commented Jul 7, 2015

screenshot from 2015-07-07 16-55-15

@gsamful
Copy link
Author

gsamful commented Jul 7, 2015

I am also a user of Arch by the way! And the same problem occurs!
@lainme

@xiehuc
Copy link
Owner

xiehuc commented Jul 7, 2015

sorry,没遇到过。暂不清楚。

2015-07-07 19:21 GMT+08:00 gsamful notifications@github.com:

I am also a user of Arch by the way! And the same problem occurs!
@lainme https://github.com/lainme


Reply to this email directly or view it on GitHub
#653 (comment).

@juvevood
Copy link

juvevood commented Jul 8, 2015

我也是,qq基本瘫痪了,登录后qq消息窗口刚出来就卡死,强制退出后重新登录会稍微好点,单马上又会陷入死循环……

@xiehuc
Copy link
Owner

xiehuc commented Jul 8, 2015

有没有gdb调试信息之类的?

另外后端是用的purple吗?

2015-07-08 10 26 42

@juvevood
Copy link

后端是用的purple

@xiehuc
Copy link
Owner

xiehuc commented Jul 10, 2015

大概是因为启动时消息太多,
要是能知道具体是什么地方卡住的就好了。

在 2015年7月10日,上午10:54,juve notifications@github.com 写道:

后端是用的purple


Reply to this email directly or view it on GitHub #653 (comment).

@juvevood
Copy link

如下gdb复现了一次卡死的过程,其他信息不知道在哪里可以找到
Starting program: /usr/bin/pidgin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffca9fe700 (LWP 4022)]
[Thread 0x7fffca9fe700 (LWP 4022) exited]
[Jul 13 15:51:26] WARNING[4010]: http.c:751 check_multi_info:
async retcode:28 Timeout was reached
Verify code: !FVU
[New Thread 0x7fffadffb700 (LWP 4039)]
[Thread 0x7fffadffb700 (LWP 4039) exited]
[Jul 13 15:51:30] WARNING[4010]: http.c:751 check_multi_info:
async retcode:6 Couldn't resolve host name
[Jul 13 15:51:30] WARNING[4010]: http.c:751 check_multi_info:
async retcode:6 Couldn't resolve host name

Program terminated with signal SIGKILL, Killed.
The program no longer exists.

@juvevood
Copy link

这次运行了一段时间挂了,截图最后部分
[Jul 13 15:55:58] WARNING[4114]: http.c:761 check_multi_info:
retry left:2
[Jul 13 15:55:58] WARNING[4114]: http.c:751 check_multi_info:
async retcode:6 Couldn't resolve host name
[Jul 13 15:55:58] ERROR[4114]: info.c:1574 group_detail_back:
Parse json object error: {"retcode":6}
[Jul 13 15:55:59] ERROR[4114]: info.c:1574 group_detail_back:
Parse json object error: {"retcode":6}
[New Thread 0x7fffaffff700 (LWP 4159)]
[Thread 0x7fffaffff700 (LWP 4159) exited]
[Jul 13 15:57:25] WARNING[4114]: http.c:751 check_multi_info:
async retcode:28 Timeout was reached
[Jul 13 15:57:25] WARNING[4114]: http.c:761 check_multi_info:
retry left:3
[Jul 13 15:59:50] WARNING[4114]: http.c:751 check_multi_info:
async retcode:28 Timeout was reached
[Jul 13 15:59:50] WARNING[4114]: http.c:761 check_multi_info:
retry left:2
[Thread 0x7ffff7fa8900 (LWP 4114) exited]

Program terminated with signal SIGKILL, Killed.
The program no longer exists.

@xiehuc
Copy link
Owner

xiehuc commented Jul 15, 2015

async retcode:6 Couldn't resolve host name
是说,无法连接到服务器。
要么是网络不好,要么是开了代理。

@ghost
Copy link

ghost commented Jul 20, 2015

我这里是没有任何提示就卡死,经常是打开pidgin-lwqq一段时间然后pidgin就死了,之前0.5版的好像还没这样频繁死过,不过0.6增加了好些功能很不错,另外不知道0.6.1增加了些什么,稍后有空更新看看

@ghost
Copy link

ghost commented Jul 20, 2015

学长该是已经毕业了吧

@xiehuc
Copy link
Owner

xiehuc commented Jul 21, 2015

毕业了。
0.6.1 主要是修正了弹验证码的时候无法登录的情况。
另外dev分支有一个use after
free的错误修正,不知道和卡死有没有关系。

在2015年07月21,上午 3:13,rtlix notifications@github.com
写道:

学长该是已经毕业了吧


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants