OS X Modem problem found, solved?

amorphamorph
Posted:
in macOS edited January 2014
There's a thread in the <a href="http://forums.macnn.com/cgi-bin/ultimatebb.cgi?ubb=get_topic&f=46&t=003793"; target="_blank">MacNN forums</a> about it.



Looks like they found the culprit, and they're going to squash it. I hope this comes out for 10.1.3.



It's about time, although I can't blame them for the difficulty involved in tracking down a low-level malloc() bug that hit hardest when memory was heavily fragmented. Talk about obscure...

Comments

  • Reply 1 of 5
    ghost_user_nameghost_user_name Posts: 22,667member
    Why did it take Apple so long to find it? Seems rather sloppy to me.
  • Reply 2 of 5
    airslufairsluf Posts: 1,861member
  • Reply 3 of 5
    ghost_user_nameghost_user_name Posts: 22,667member
    Yea I read it. Still seems rather sloppy to me. I thought Apple was run by pros?
  • Reply 4 of 5
    junkyard dawgjunkyard dawg Posts: 2,801member
    $100 says this bug fix is not in 10.1.3. It will not be in 10.1.4, either, nor will it be in 10.2. Apple is never going to fix this bug.
  • Reply 5 of 5
    buonrottobuonrotto Posts: 6,368member
    Allow me to complete the thought of the previous two posts...



    *ahem*



    "Apple is doomed."







    Back to your regularly scheduled bug fix thread.
Sign In or Register to comment.