#1675: Licq runaway process whenever use Search History
---------------------+------------------------------------------------------
Reporter: wed | Owner:
Type: defect | Status: new
Priority: high | Milestone: 1.3.7
Component: None | Version: 1.3.6
Resolution: | Keywords:
---------------------+------------------------------------------------------
Changes (by flynd):
* priority: highest => high
Old description:
> Whenever I use "search" in History with Licq 1.3.6 in Mandriva 2009.1, I
> get a runaway process using 100% CPU. With luck I can kill it and get the
> attached licq.backtrace.
>
> The console shows:
>
> [...@localhost ~]$ licq
> Backtrace (saved in /home/w/.licq//licq.backtrace):
> licq(licq_handle_sigabrt+0x38a) [0x812c05a]
> [0xffffe400]
> [0xffffe424]
> /lib/i686/libc.so.6(gsignal+0x50) [0xb7a90c00]
> /lib/i686/libc.so.6(abort+0x188) [0xb7a92668]
> /lib/i686/libc.so.6 [0xb7ad1f63]
> /lib/i686/libc.so.6 [0xb7ad5e75]
> /lib/i686/libc.so.6(realloc+0x42) [0xb7ad67e2]
> /usr/lib/libQtCore.so.4(_Z8qReallocPvj+0x23) [0xb73689b3]
> [0xa5d9078]
> Attempting to generate core file.
>
> Licq has encountered a fatal error.
> Please report this error either by creating a new ticket at
> http://trac.licq.org/ or by sending an e-mail to the mailing list licq-
> d...@googlegroups.com (you must be registered to be able to post, see
> http://trac.licq.org/wiki/MailingList).
>
> To help us debug the error, please include a full description of what you
> did when the error occurred. Additionally, please include the following
> files (if they exist):
> /home/w/.licq//licq.backtrace
> /home/w/.licq//licq.backtrace.gdb
>
> Thanks, The Licq Team
> Aborted
New description:
Whenever I use "search" in History with Licq 1.3.6 in Mandriva 2009.1, I
get a runaway process using 100% CPU. With luck I can kill it and get the
attached licq.backtrace.
The console shows:
{{{
[...@localhost ~]$ licq
Backtrace (saved in /home/w/.licq//licq.backtrace):
licq(licq_handle_sigabrt+0x38a) [0x812c05a]
[0xffffe400]
[0xffffe424]
/lib/i686/libc.so.6(gsignal+0x50) [0xb7a90c00]
/lib/i686/libc.so.6(abort+0x188) [0xb7a92668]
/lib/i686/libc.so.6 [0xb7ad1f63]
/lib/i686/libc.so.6 [0xb7ad5e75]
/lib/i686/libc.so.6(realloc+0x42) [0xb7ad67e2]
/usr/lib/libQtCore.so.4(_Z8qReallocPvj+0x23) [0xb73689b3]
[0xa5d9078]
Attempting to generate core file.
Licq has encountered a fatal error.
Please report this error either by creating a new ticket at
http://trac.licq.org/ or by sending an e-mail to the mailing list licq-
d...@googlegroups.com (you must be registered to be able to post, see
http://trac.licq.org/wiki/MailingList).
To help us debug the error, please include a full description of what you
did when the error occurred. Additionally, please include the following
files (if they exist):
/home/w/.licq//licq.backtrace
/home/w/.licq//licq.backtrace.gdb
Thanks, The Licq Team
Aborted
}}}
--
Comment:
That backtrace looks a bit short. Do you have a licq.backtrace.gdb? If so
please upload it as well. Otherwise could you run licq through a gdb and
generate a stack trace of all threads ("thread apply all bt") when it
hangs?
Does this happen always or just sometimes? Does it matter what you search
for? Do you have checkboxes for match case or regular expression active?
--
Ticket URL: <http://trac.licq.org/ticket/1675#comment:1>
Licq <http://www.licq.org/>
Licq - an instant messaging client for UNIX.
