Issue: Bowser crash !!!

Are you aware of a specific wiki page it was crashing on? I've been on your wiki for about an hour now and I haven't had a problem.

However I noticed some pages had about 20 full-size images, which requires the browser render over 10MB of data on those pages. Although the appearance of the images may have changed in 4.0.2, the amount of image data sent to the browser should be the same as before 4.0.2. Again, I haven't had any trouble viewing these pages, but I did fix the appearance for you so they at least fit on the screen (10 MB still gets received by the browser).

In my experience Firefox crashes often no matter what web pages you're looking at. It seems that there has been a serious memory leak in Firefox (possibly related to Firebug, possibly Flash) for years now that has still not been addressed by the Firefox devs. It's why I made the switch to Chrome as my default browser a long time ago.

Activate the Wiki And Test it!

Fixed several conditions where VaultWiki wasn't able to generate thumbnails for large images. Your image-heavy pages should now send less data to the browser for most images. However, I still don't know if you were having trouble due to the images since you haven't said what page you were viewing when the browser crashed.

As I mentioned above, Firefox is not very good about memory use. It will keep consuming memory until the browser crashes. Even after that, you sometimes need to restart the computer to free the memory. This may give you the false impression that VaultWiki has caused the browser to crash. In reality, it doesn't matter what web sites you have open:

With Firebug / Developer Tools enabled on at least one tab, Firefox will drink up a few bytes of memory every second that you move the mouse cursor, even if you are moving it on a tab that doesn't have Firebug open. Closing Firebug stops new memory from getting consumed, but it doesn't free the eaten memory. If you have many tabs open, or Firefox has been open for a long time, the memory consumption can grow quickly.

In Firefox, viewing any page with a Flash element will cause the consumption to increase more quickly. Removing the Flash element via Firebug or closing the tabs that contain Flash do not free the memory either.

After Firefox has used so much memory, it is not available to other processes like Chrome or IE. If you use either one while Firefox is eating memory, or if there is not enough memory left after Firefox has crashed, they will probably crash too. This is at no fault of Chrome or IE or any of the pages you are viewing in those browsers.

These are just some behaviors I notice with Firefox on a daily basis.

Changing the big images to lower quality would solve this problem ?

I don't know for sure. Depends if that what was causing your browser to crash or if it was something else. As I mentioned I was on your wiki for a long time today and it didn't crash. At times it took a long time to load or do something, but that was expected based on the image sizes.

If the issue was image sizes alone, it should be resolved for now. Your installation should be able to generate thumbnails which will load much faster and use less memory.

I do not have any issues using the wiki at http://geislingen.net/wiki/ or using any other page / forum on your site in any browsers. It seems to load in a normal amount of time and does not crash at all.

Have you tried:
- Restarting your computer
- Trying the web site from a different computer
- Clearing your browser's cache

Note that the wiki is right now only available for admins, so there is no reason to disable the add-on until you can figure out the problem. Unless the site crashes at /forums from a different computer when you are viewing as a guest.

Hi,

News:

As guest all browsers works fine with the page at my computer

as admin firefox crashes at the wiki startpage - after clearing the cache, after computer restart.
chrome loading and loading...

on iPhone it works perfect.
Other computers it seems to work

What can be the problem with my computer ???

Can you set the wiki-permissions back? I don't know what settings you have done...

In Options > VaultWiki: Site Config, I unchecked "Wiki Active". If you check it, it will be available to guests.

I'm not sure what might be the problem on your computer. You can start going through troubleshooting checklists for your browsers that do crash. e.g: http://kb.mozillazine.org/Firefox_crashes

Internet Explorer works, FF and Chrome not - scary... No idea what the problem is since a few days...
I deleted all cache, cookies, etc. - nothing works... browsers hang up after 3-4 pages!

Try downloading 4.0.2 build 003 and replacing the file vault/resources/js/base.js on your server with the one from the ZIP.

I replaced the file.

Now it works with chrome and IE.
Firefox is still crashing at my computer...

Did you clear Firefox's cache after uploading the new file?

Yes,
second or third page on the site crashes the firefox for me...