konqueror crashed with SIGSEGV in KJS::Collector::markProtectedObjects()

[Kaltsi]

Binary package hint: kdebase

Jan 19 18:59:25 kub-kal kernel: [208823.163959] konqueror[32445]: segfault at dip b6bbc960 sp bf97f5d8 error 4 in libQtGui.so.4.4.3[b6935000+8dd000]

The trace upload crashed :(
Description: Ubuntu jaunty (development branch)
Release: 9.04

kdebase:
  Installed: (none)
  Candidate: 4:4.1.96-0ubuntu2
  Version table:
     4:4.1.96-0ubuntu2 0
        500 http://archive.ubuntu.com jaunty/main Packages

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/konqueror
Package: konqueror 4:4.1.96-0ubuntu2
ProcCmdline: konqueror https://bugs.launchpad.net/ubuntu/+source/kdepim/+filebug/pOxoihzSQw5P2e2EoHxpWPj0qqF?field.title=kontact+crashed+with+SIGSEGV+in+KCal%3A%3ACalendarResources%3A%3AresourceManager%28%29
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
Signal: 11
SourcePackage: kdebase
StacktraceTop:
 KJS::Collector::markProtectedObjects ()
 KJS::Collector::collect () from /usr/lib/libkjs.so.4
 KJS::Interpreter::collect () from /usr/lib/libkjs.so.4
 ?? () from /usr/lib/libkhtml.so.5
 ?? () from /usr/lib/libkhtml.so.5
Title: konqueror crashed with SIGSEGV in KJS::Collector::markProtectedObjects()
Uname: Linux 2.6.28-4-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:KJS::Collector::markProtectedObjects ()
KJS::Collector::collect ()
KJS::Interpreter::collect ()
~KJSProxyImpl (this=0xa301c08)
~ChildFrame (this=0x9e52970)

[Connor Imes (ckimes)]

Kaltsi,
Can you please explain what you were doing when this crash occurred? How did it happen? Can you reproduce it? Thanks.

[Steve Stalcup (vorian)]

does this still happen with 4.2.0?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!