Timeline dragging does not show a wireframe of clip position

Sorry for the wait, but this issue should now be resolved with Premiere Pro 15.4.
https://helpx.adobe.com/premiere-pro/kb/fixed-issues.html
- Clip outline (shadow trail) should be visible whenever the clip is moved in the timeline.

I would highly recommend to every one having this problem to create a shortcut for "Render Audio". I for example use "Ctrl + Alt + c". Every time the bug accuse I just press it.

I also made a YouTube video on the issue because I couldn't not funde a solution on YouTube and it took me forever to find this thread. https://youtu.be/kfpcbRr3HTM

I can confirm this BUG. It's the nesting. It's almost as if it disables all the mouse functions except moving the cursor around. Clicking on another panel or unfocusing the Premiere window(alt-tab for example) unstucks you but as soon as you use scroll on the timeline with a nested subsequence it happens again. When the bug happens you can't even hover over sub-menus to expand it, which it normally does when you just hover over it.

Temp. workarounds but not fixes:
1. "Timeline → Wrench → Turn Off Audio Waveforms"
2. Render audio

Continued...

Now I have it narrowed in to it's a "nesting" problem... Kinda makes it crash...
Plus it seems to work fine with other clips in the timeline.

Experiencing the same thing, and as mentioned below the "Timeline → Wrench → Turn Off Audio Waveforms" said by Tyler will do so that you can drag and still see the clip size, but the problem is that I work a lot with the audio too, so I have to be able to see the waveform.

Also I work with nests.

Is it really so, that there is no fix for this?

I also have the same issue but rendering audio did fix it, thanks! Please fix Adobe...

I'm having the same problem. This happened when I created a nest and rendering the audio like mentioned below solved it.

I love you Tyler. struggled for about 2hours and fixed it

Having the same issue in the latest version. Clicking across to another panel and then back to my timeline fixes it for about a minute and then the same issue comes back. I wish Adobe would spend more time fixing bugs that have been in their software for two years rather than implementing ai features that have no professional use.