Welcome, Guest. Please login or register.

Author Topic: Ibrowse & jpegtmp?huh  (Read 4112 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline JetRacer

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 501
    • Show all replies
Re: Ibrowse & jpegtmp?huh
« on: May 24, 2003, 07:04:17 PM »
carls: The jpgtemp is just a quick hack by a clueless individual so that the jpeg decoder would run on a vanilla A1200. It never takes the free mem into consideration and always use the jpgtemp for storage. That is highly improper when loading html pages with >20 small jpeg images in it. People who got the ram should assign it to ram:t.

Everybody:

Keeping the IB cache in ram: speeds things up considerably. Plus it's safer that way. IB2.X leaves cache files open on exit, locked threads which makes cache files "in use", etc. You don't want it to trash your HDD. Such defect cache files will cause a crash next time you use IB to surf the same site using cache content.

The IB cache is probably responsible for 90% of all crashes.
*Zap! Zap!* Ha! Take that! *Kabooom!* Hey, that\'s not fair!