Bug 131498 - Hard lock-up with Konqueror and Gvim when browsing certain pages
Summary: Hard lock-up with Konqueror and Gvim when browsing certain pages
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-29 01:58 UTC by Ismail Onur Filiz
Modified: 2008-08-05 20:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ismail Onur Filiz 2006-07-29 01:58:36 UTC
Version:            (using KDE KDE 3.5.3)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9) 
OS:                Linux

I am experiencing what must be one of the weirdest bugs I have ever come across. The way to reproduce it is:
- Log in to a KDE session.
- Start konqueror and browse to a certain Doxygen generated page ( has caller, callee graphs, regular documentation etc. and is about 20 screenfuls ), hosted locally by Apache on the computer.
- Start gvim.
Either at this point, or when I maximize the gvim window after it appears, the computer locks up completely. Moons must have aligned properly for me:)

Some details that might be relevant:
- The computer is an IBM Thinkpad T30, with an ATI Radeon Mobility 7500 graphics card. 
- This started happening after I upgraded Xorg to the 7 series. The driver is the open source Radeon driver that comes with Xorg.
- I have a dual-monitor set-up, laptop LCD + a Samsung LCD, both running in 1280x1024 resolution, using "MergedFB" and "MergedXinerama" modes of the Radeon driver.
- I have experienced similar lock-ups when I ran firefox too, which makes me think it might be a gui toolkit problem.
- If I don't immediately run gvim after the page loads, but browse to other pages and come back, the probability of the lock-up decreases.
- If the page I open is another page for another class, generated from the same codebase with same Doxygen parameters, it doesn't lock up.
- I didn't have these lock-ups when I was using Xfce as the desktop environment.
- The problem is independent of KDE settings, since I could reproduce with a newly created user.

Unfortunately I cannot post the page that helps me consistently reproduce, since it is confidential. I wouldn't expect anybody other than me to be able to reproduce it anyhow, since it looks like a very particular set-up triggers the bug. What I am hoping is instructions and suggestions as to how I can debug this further. Thanks in advance.
Comment 1 George Goldberg 2008-08-05 20:49:46 UTC
Hi. Since there is not really anything we can do to debug this issue, I am closing it. Please feel free to reopen the report if you can still reproduce it with a recent version of KDE, *and* provide a sample file that triggers the lockup.