This issue has been lingering for quite some time and despite similar questions, I have not come across a satisfactory solution. The problem lies in the fact that the SOURCE used to step through the code does not refresh with every page load. Disabling the cache hasn't helped as it's not the browser cache but the DEBUGGER SOURCE cache causing problems.
In my web application (Struts2 and Tomcat), the main page features a title bar and left menu, with an iframe loading various JSPs in the center content. While most navigation is handled by one 'action' with different results displaying different pages, the challenge arises when the NAME in the chrome debugger SOURCES pane fails to change upon navigation. Although the actual page changes, Chrome fails to update the source in the debugger window. This means that if there is a 'debugger;' line on 200 in the loaded page, it stops at the old source at line 200 rather than the current source being executed. Despite revealing the real source in the Network panel, the debug source remains unchanged.
Question: How can I work around this Chrome bug and compel the source to reload in the debugger display?
UPDATE: Contrary to some assumptions, this issue differs from others. David Fahlander's answer appears to resonate with my concerns. The javascript source successfully refreshes and displays correctly in the RESOURCES and NETWORK panes. However, the new source fails to refresh in the SOURCE pane where debugging takes place, creating obstacles in troubleshooting code invisibly.