Dock madness!

Posted:
in macOS edited January 2014
:eek: Can anyone explain just what the hell is going wrong with the Dock in this movie?



<a href="http://brad.project-think.com/movies/DockBuggin.mov"; target="_blank">http://brad.project-think.com/movies/DockBuggin.mov</a>; (1.82 MB)



This has happened several times for me in various versions of Mac OS X (this time with 10.1.1) and I just finally caught this bug in action as shown by the clip. Weird stuff, huh? First of all, the Dock was set to auto-hide, but it got stuck up there and I couldn't get it to hide again. I was navigating with only the mouse up until the background of the Dock disappeared and clicking on the Dock had no response. Clicking on the resize bar did nothing from the beginning anyway. Then, I tried cmd-tab which successfully revived the Dock but produced an odd horizontal line at the bottom of the screen. Also, notice that the Terminal has a single black dot under it. I've seen this happen many times; quitting apps often leaves a piece of the triangle, as it did here.



Unfortunately, I can't seem to reproduce this bug at will. It just happens sometimes. As you can see, I'm obviously not running any weird apps that would cause this.



Has anyone else here experienced something like this?



[ 12-06-2001: Message edited by: starfleetX ]</p>

Comments

  • Reply 1 of 4
    leonisleonis Posts: 3,427member
    HA! I have never seen this before :eek:
  • Reply 2 of 4
    buonrottobuonrotto Posts: 6,368member
    Zat's a new one. No pattern? No preamble or routine that precedes it? Curious indeed!
  • Reply 3 of 4
    :eek: <img src="graemlins/bugeye.gif" border="0" alt="[Skeptical]" />



    [insert obligatory feedback form link here]
  • Reply 4 of 4
    [quote] :eek: <img src="graemlins/bugeye.gif" border="0" alt="[Skeptical]" /> <hr></blockquote>My thoughts exactly. [quote]Originally posted by BuonRotto:

    <strong>Zat's a new one. No pattern? No preamble or routine that precedes it? Curious indeed!</strong><hr></blockquote>That's right. IIRC, it usually may happen after some cmd-tabbing and/or cmd-H'ing.



    By the way, zats notta new one for me. I've always done clean installs of X, FYI, starting with a fresh Library and Home each time. I will admit to doing rigorous and extensive tests of the various parts of X and must say that this type of bug has reared its ugly face only a few times since way back in the pre-4K78 days. It's a rare "treat" to catch it in action to the extent as seen above!



    I'm off to write my feedback report now...
Sign In or Register to comment.