Safari Browser Problems
Safari Browser is designed and developed by Apple. It can be used on iPad, iPhone, iPod Touch, Mac and PC. Safari enables you to display your favorite websites in a graphically rich page with up to 24 thumbnails. It makes it simple for users to view the websites they want to visit. Apple claims it to be the fastest browser available when compared with other web browsers. Safari is leading the way to a standards-based Internet browser by adopting HTML5 audio and video tags and other advancements. It allows users to enjoy a rich-media and fast-loading Internet experiences. Safari also offers security protection for its users and provides Private Browsing. Despite all the advantages, this browser has various problems.
A security risk has been found within the Safari browser. This risk is present in a feature which can reveal a user's personal information. The feature is called Auto Fill, which was developed as a component of the browser to save users' time by filling out numerous forms, retaining the data on their computer's and loading the information when users use the relevant forms again. The vulnerability in the browser can allow intruders to access personal information and thus pose threats to a user's privacy. The exploitation of this vulnerability is quite easy, according to White Hat Security. Of course, a simple solution is to quit using the Auto Fill Feature.
Safari has a serious problem called memory leak, and it seems to be a more noticeable issue in the latest versions. A memory leak emerges when the browser loads web pages and utilizes more and more of your computer's memory until the system is frozen. You have to restart the system to overcome the problem.
Safari downloads files to the OS desktop or downloads a directory without requesting user permission. This put users' computers at risk by downloading malicious applications. Apple doesn't treat this as a security issue but a further improvement in downloading. However, this issue, along with another problem, which is Safari fails to warn users when a local resource tries to trigger client-side scripting, causes potential risks to users.