主题：问题: Firefox crash -- truth

我用Firefox最大的问题就是当它crash的时候, 会导致储存的cache全部丢失(cookies好象没问题), 再次启动时不得不重新下载许多以前下载过的内容. 虽然所有的browser都会crash, 但自动clear cache on crash却是少见.

这里有高人知道解决办法摸?

看看这里，也许你能找到点什么帮助！

还有，是不是在访问特定的webpage的时候crash？

我用Firefox(windows/solaris)很少遇到过crash的情况。

Firefox的升级做得不好，尤其是一些插件的兼容性。如果你经常crash，可以考虑删除所有文件重装一次，你可以保留一些文件－－prefs.js

下载下来，Uninstall以前的，然后Install现在这份新的。好在FireFox不大，如果有个三五十兆，那可讨厌了。从1.0正式发布以来，我已经"升级"四次了。看来在Patch问题上，Firefox还没有解决问题的办法！

http://wiki.mozilla.org/Software_Update

查查你的Add Remove Programs

以前的1.0版本一样有此问题.

Extensions: Adblock, LastTab, FlashGot, User Agent Switcher

相比IE, Firefox还算是稳定的. 但不知为何crash时要清空cache, 异常退出也不至于把文件删除/清零啊, 顶多丢失latest changes而已.

除非有人take time to fix the core, mozilla那帮人似乎并不热心. 此bug是mozilla的设计问题, 已有数年历史, 曾被列为won't fix. 现在reopen了, 但fix还是遥遥无期. 怎么IE和Opera就没有这个问题呢?

外链出处

If Mozilla crashes, then all the images in the cache are lost (and presumably

the cached HTML pages as well). This is easy to reproduce: just go to a site

with a lot of graphics (like http://megatokyo.com), do "killall -9 mozilla-bin",

then restart Mozilla and go back to that site; it will start reloading all of

the images.

This is by design. The cache is primarily an optimization. Rather than add a

bunch of extra code to verify it and fix any potential corruption, we toss it

and start again.

unfortunately, there is no code to detect a bad cache. what mozilla does

currently is detect that the cache was never closed after being previously

opened. what this means simply is that when the cache is opened, a flag is set

indicating that its on disk representation is dirty (i.e., possibly incomplete).

at shutdown everything is sync'd to disk and the dirty flag is cleared.

however, what you are proposing requires determining if a cache is corrupt or

not, and that is a very complicated problem to solve. we are no where close to

having enough support in gecko to determine if the cache files are consistent.

i think you do not understand how the cache is implemented. in a nut-shell (and

this explains why this bug is hard to fix), the index of cache entries is an

in-memory data structure that is only written to disk when the browser exits

cleanly. however, data files are written as we load pages. the result is that

the data files on disk are not in sync (at all) with the index of cache entries

stored on disk. hence, if we do not shutdown cleanly, we do not have a

meaningful index of cache entries on disk.

the "solution" that you propose would cause the browser to crash or load

incorrect content in many cases.

i understand that this bug matters to some people, but so do many other bugs.

fixing this bug is a non-trivial task. if it were a trivial task, we wouldn't

be having this discussion. please try to temper your comments in the future.

getting angry doesn't solve anything.

FYI, we are planning a rewrite of the cache based on SQLite. Part of this

rewrite should solve this bug (hopefully). If you are interested, see the

beginnings of this code here:

http://lxr.mozilla.org/mozilla/source/netwerk/cache/src/nsDiskCacheDeviceSQL.cpp

application? Splitting it into many small pieces (i.e. DLLs/shared libraries) will hurt performance, because function call across shared library is slower than direct call.

I remember there was a time that Mozilla (the all-in-one suite) came with many many small shared libraries. The developers did profiling and decided to put them together.

Actually, there are quite few DLLs under firefox folder. I guess they are not key components.

原理不明的说，从行为来判断，似乎随时把所有tab里的内容备份。我有过firefox崩溃过后所有tab内容恢复的经历。

http://extensionroom.mozdev.org/more-info/sessionsaver