Based on custom cursors, Apple’s macOS Monterey memory packages

These are unsatisfactory desires for memory if they use certain materials. And these are: Apple’s macOS Monterey, iGiant’s new desktop operating system release.

Shortly after the OS update was released on October 25, Apple customers – at least those who avoided installation problems – began to notice that some apps noticed too much memory, so the the system will crash or stop.

Similar reports are available for Adobe Creative Cloud applications, Microsoft Office, Cinema 4D, and Pages, to name but a few.

Mozilla’s Firefox also applies – 79GB of memory is huge, especially for a browser known for memory usage. Following a Oct. 10 virus report, posted shortly before the release of macOS Monterey, Mozillans concluded that Apple’s new operating system had been hampered by a memory leak that occurred when an application was using a custom cursor.

“On macOS 12 Monterey, the use of abnormal cursor size or colors causes a large memory leak in Firefox,” the virus report explained. “The Firefox 94 version includes a fix that reduces memory loss, but the problem can still occur. The problem has been reported to Apple and it is expected to be updated in the future to macOS 12. ”

A memory leak occurs when the application code partitions and then fails to free up that memory for reuse after it is no longer needed, leading to the storage of existing memory. When memory is running this way and it is not clearing, the memory supply will be weakened and the applications will be turned off.

In a blog post on Monday, software developer and Electric Light Company founder Howard Oakley suggested that the dancing took place from a group of programs in the Access Choice Pan, which provides visual conversion controls.

Oakley wrote “The church appears to occur when the type of arrow changes, for example from a standard arrow to an I-beam for insertion,” Oakley wrote. “The most likely thing is that, when the indexer is customized using those settings in the pane, the memory used by the previous index is not independent following the change in the type of pointer.”

Via Twitter, developer Steve Troughton-Smith noted that the issue could be followed by Apple replacing the old Objective-C code – where memory is manually managed – with Swift code, which is essentially automatic memory management.

There are almost certainly other memory leaks in macOS Monterey, as they are previous device releases and in apps. Software full of bugs. But the large number of applications just means that Apple should send a refund sooner rather than later.

We will be happy to hear your thoughts

      Leave a Reply

      AppleiPhonestop - Apple iPhone News and Rumours All Day
      Enable registration in settings - general
      Compare items
      • Laptops (0)