konqueror hangs forever when opening pdf (nondeterministic)

[Georg Sauthoff]

Binary package hint: konqueror

Hi,

I am using kubuntu edgy edge (6.10). I observed that konqueror hangs forever (no screen updates, no user input possible) when I click on a pdf file.

Normally when I click on a pdf file, it is displayed inside konqueror (via the kpdf kpart).

This issue is not deterministic reproducible. I.e. it is not observable at every pdf file and it is hard to reproduce.

This time the konqueror process was runnung a long time (>10 days including suspend-to-ram periods) and I have opened > 15 tabs).

An attached strace shows me only:
futex(0x85e39dc, FUTEX_WAIT, 2, NULL <unfinished ...>

I made a short and a full gdb backtrace (with -dbg packages installed). I will try to attach the short backtrace log to this bug - if you need the full backtrace, I can send it, too.

Also, I have a manually generated core file available - thus, I am able to issue some gdb commands to it.

Best regards

[Georg Sauthoff (g-sauthoff)]

gdb commands: attach, info threads, bt, detach

[Georg Sauthoff (g-sauthoff)]

I observed another konqueror freeze/hang while clicking on a pdf link from a web page.

This time the konqueror process was running ~2h and only 2 tabs were open.

A gdb backtrace is attached.

[Georg Sauthoff (g-sauthoff)]

I reported it at the kde bug tracker, too. It looks like the problem is specific to (K)ubuntu, because Ubuntu uses a patched kpdf - which uses libpoppler. And the kpdf kpart hangs in libpoppler.

This wrote Pino Toscano as a comment:
http://bugs.kde.org/show_bug.cgi?id=139877#c3

Ok, how do I annotate this bug report, that it affects kpdf and libpoppler?

[Sarah Kowalik (hobbsee-deactivatedaccount)]

upstream says this crash is in poppler.

[Sarah Kowalik (hobbsee-deactivatedaccount)]

to attach, hit "also effects...upstream" and enter the URL.

[Sebastien Bacher (seb128)]

Could you try if the issue is still there on gutsy or hardy?

[Rich Johnson (nixternal)]

I am fix releasing this since I cannot recreate the issue at all with KDE 3.5.8, KDE 3.5.9, nor KDE 4.0.1, and also due to the fact that the reporter hasn't responded. Thanks!