|
[haiku-development]
||
[Date Prev]
[04-2008 Date Index]
[Date Next]
||
[Thread Prev]
[04-2008 Thread Index]
[Thread Next]
[haiku-development] Re: BFS and write back problems
- From: dolgov <dolgov@xxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 02 Apr 2008 13:19:19 +0300
Axel Dörfler wrote:
This probably happens for you that often, because other OS' don't crash
that often with Firefox in use.
I use SeaMonkey mostly, and it don't crash itself (and OS) much more
frequently than that in Windows or Ubuntu.
But sure, at home I use BeOS 99% of time.
Also BeOS has a very poor cache/transaction flush management: if the
cache is constantly in use (ie. when you're playing some songs in the
background), BeOS will never flush the cache, unless a transaction is
actually finished (and not just joined with the previous one).
Therefore I pretty often "sync" in BeOS manually (as Dano is not that
stable).
I thought about adding flush() in several places in code related to file
transactions with ifdef BeOS, but it seems too hacky and troublesome.
Also I wasn't sure if it has desired effect for files, open for browser
lifetime - until proper close() call. And this is how Mozilla seems
handling those files, like prefs.js.
Regards, Sergei "fyysik" Dolgov
|
|
