[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 110318] Massive Lock-Ups While Web Browsing during periods of
From:       <jdxyz () juno ! com>
Date:       2009-12-05 15:57:37
Message-ID: 20091205155737.BC6EC28FD4 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=110318





--- Comment #43 from  <jdxyz juno com>  2009-12-05 16:57:06 ---
sam,
 you said, Sami Liedes <sliedes cc hut fi>  2009-12-01 23:11:54 ---
As I see it, it's the syncing that's the problem, and specifically that calling
fsync() does is effectively say: Write this out as soon as
possible, block until that is done. It's a tool to play on exact ordering of
writes to facilitate recovery.
first question, did you access the fsync? or kconfig and how.

KDE folks want, since they don't depend on the exact ordering of
writes for recovery, is: Write this out as soon as possible, but also return as
soon as possible (don't block until it's done). 
 makes sense, please refer to question #1
ffox seems to try harder when erasing personal info, cach, etc when closing. I
notice that something is sucking ram after browser startup. I suspect adware or
spyware designed for linux. imho

good luck to all,
jd



____________________________________________________________
Nutrition
Improve your career health. Click now to study nutrition!
http://thirdpartyoffers.juno.com/TGL2141/c?cp=1un6vkbKCDop5sF6BbZcJwAAJ1C5rjx__MSrDJtOPAULkXkGAAYAAAAAAAAAAAAAAAAAAADNAAAAAAAAAAAAAAAAAAASQwAAAAA=


-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.


[prev in list] [next in list] [prev in thread] [next in thread]