Bug 227633 - crash in kdebase-workspace during starting Konqueror
Summary: crash in kdebase-workspace during starting Konqueror
Status: RESOLVED DUPLICATE of bug 227635
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-19 09:04 UTC by palo.liska
Modified: 2010-02-26 16:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
backtrace (10.02 KB, text/plain)
2010-02-19 09:10 UTC, palo.liska 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description palo.liska 2010-02-19 09:04:31 UTC 
Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    Fedora RPMs

abrt 1.0.3 detected a crash.

How to reproduce (or how bug was made)
-----
1.Running firefox in background for longer time (>24hours)
  with a lot of tabs opened containing javascript (e.g. ebay.com).
2.Try to start Konqueror


Comment: It is probably not systematic. It happend after more than 24 hours of
running fedora with firefox.
Attached file: backtrace
cmdline: plasma-desktop --nocrashhandler
component: kdebase-workspace
executable: /usr/bin/plasma-desktop
kernel: 2.6.31.12-174.2.3.fc12.i686
package: kdebase-workspace-4.3.4-6.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
Comment 2 palo.liska 2010-02-19 09:10:10 UTC 
Created attachment 40918 [details]
backtrace
Comment 3 palo.liska 2010-02-19 09:16:53 UTC 
See https://bugs.kde.org/show_bug.cgi?id=227635
Comment 4 Dario Andres 2010-02-19 22:45:30 UTC 
- Which application crashed ? Konqueror ? Plasma ?
The backtrace is not really complete... may be it is a Qt bug or the memory was too full (because of the long-running Firefox)?
Regards
Comment 5 palo.liska 2010-02-22 09:15:05 UTC 
Konqueror crashed.
Comment 6 Dario Andres 2010-02-26 16:02:27 UTC 

*** This bug has been marked as a duplicate of bug 227635 ***