Some files don't show up in Sources

23,516 views
Skip to first unread message

da...@windward.net

unread,
Apr 3, 2014, 12:38:22 PM4/3/14
to google-chrome-...@googlegroups.com
Hi;

The Sources tree does not list all files, just the ones it knows are in use. How can I get other files in there so I can set breakpoints in them before they execute for the first time?

Also, how do I get worker .js files in the Sources? Generally they don't show and Ctrl-O doesn't list it. (And sometimes they do show up - no idea why when that happens.)

Vsevolod Vlasov

unread,
Apr 7, 2014, 5:05:27 AM4/7/14
to Google Chrome Developer Tools
Workers debugging could only be done in a separate worker front-end currently. You could open it by clicking a link in the workers list in Sources panel sidebar. You could also check a checkbox that makes all workers break on start.

As for debugging the scripts that are loaded dynamically you have two options:
1) Wait until the script is loaded, set the breakpoint and reload the page. the breakpoint will be kept in the VM and debugger will pause on it when needed.
2) Use DevTools workspaces to add a local folder and map it to the network resources so that the dynamically loaded script file is always available and you could set breakpoint in it.


--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/e36ca2b3-9245-490b-aadc-0a5f2be95101%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

da...@windward.net

unread,
Apr 7, 2014, 9:07:50 AM4/7/14
to google-chrome-...@googlegroups.com
Hi;

How exactly do I:
    1. open it by clicking a link in the workers list in Sources panel sidebar
    1. check a checkbox that makes all workers break on start.
    1. (add a local folder and) map it to the network resources
    I tried to find the first 2 items and could not. I did find how to add a local folder, but could not find how to map it.

    ??? - thanks - dave

    Vsevolod Vlasov

    unread,
    Apr 7, 2014, 9:29:12 AM4/7/14
    to Google Chrome Developer Tools
    1., 2. Look under the Workers in the Sources panel sidebar. (See the bottom of the attached screenshot)
    3. http://www.html5rocks.com/en/tutorials/developertools/revolutions2013/#toc-workspaces


    --
    You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
    workers.png

    da...@windward.net

    unread,
    Apr 10, 2014, 12:07:57 PM4/10/14
    to google-chrome-...@googlegroups.com
    Hi;

    Ok, a little progress, but not much.
    I added the folder, but when I right click to "map to network resource" I get:

    So no way to actually set it.

    Also, How exactly do I:
    1. open it by clicking a link in the workers list in Sources panel sidebar
    2. check a checkbox that makes all workers break on start.
    thanks - dave


    On Monday, April 7, 2014 7:29:12 AM UTC-6, Vsevolod Vlasov wrote:
    1., 2. Look under the Workers in the Sources panel sidebar. (See the bottom of the attached screenshot)
    3. http://www.html5rocks.com/en/tutorials/developertools/revolutions2013/#toc-workspaces
    On Mon, Apr 7, 2014 at 5:07 PM, <da...@windward.net> wrote:
    Hi;

    How exactly do I:
    1. open it by clicking a link in the workers list in Sources panel sidebar
    2. check a checkbox that makes all workers break on start.
    3. (add a local folder and) map it to the network resources
    I tried to find the first 2 items and could not. I did find how to add a local folder, but could not find how to map it.

    ??? - thanks - dave


    On Monday, April 7, 2014 3:05:27 AM UTC-6, Vsevolod Vlasov wrote:
    Workers debugging could only be done in a separate worker front-end currently. You could open it by clicking a link in the workers list in Sources panel sidebar. You could also check a checkbox that makes all workers break on start.

    As for debugging the scripts that are loaded dynamically you have two options:
    1) Wait until the script is loaded, set the breakpoint and reload the page. the breakpoint will be kept in the VM and debugger will pause on it when needed.
    2) Use DevTools workspaces to add a local folder and map it to the network resources so that the dynamically loaded script file is always available and you could set breakpoint in it.


    On Thu, Apr 3, 2014 at 8:38 PM, <da...@windward.net> wrote:
    Hi;

    The Sources tree does not list all files, just the ones it knows are in use. How can I get other files in there so I can set breakpoints in them before they execute for the first time?

    Also, how do I get worker .js files in the Sources? Generally they don't show and Ctrl-O doesn't list it. (And sometimes they do show up - no idea why when that happens.)


    --
    You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

    Vsevolod Vlasov

    unread,
    Apr 11, 2014, 2:54:40 AM4/11/14
    to Google Chrome Developer Tools

    da...@windward.net

    unread,
    Apr 11, 2014, 10:08:35 AM4/11/14
    to google-chrome-...@googlegroups.com
    The video helped - it showed how to set Workers - pause on start. And when that box is checked, then you do get the new window coming up with the debug control for the worker. IF THAT BOX IS NOT CHECKED THEN YOU GET NO DEBUGGING FOR THE WORKER. Not even if you have a "debugger;" in the worker code.

    However, I still can't do the map to network resource - how do I do that? (My problem is in the screenshot earlier in the thread - the window for map to network resource doesn't let you do anything.)

    ??? - thanks - dave

    Ujjwal Singh

    unread,
    Jun 21, 2015, 2:23:41 PM6/21/15
    to google-chrome-...@googlegroups.com, da...@windward.net
    Try removing the old work-space folder, if any.

    brad jareczek

    unread,
    Nov 13, 2015, 11:36:03 AM11/13/15
    to Google Chrome Developer Tools, da...@windward.net
    I have battled trying to find my resource files for hours... I must have inadvertently excluded them or something.  I finally stumbled on this little gem of a button which get me back up and running in seconds:  "Restore defaults and reload".  The other Workspace section may help you, but it did not help me.

    Ganesh Kudale

    unread,
    Jan 13, 2016, 3:53:19 PM1/13/16
    to Google Chrome Developer Tools, da...@windward.net
    Fantastic Brad :) thanks lot. 

    Mike Sinn

    unread,
    Dec 7, 2016, 2:59:40 AM12/7/16
    to Google Chrome Developer Tools, da...@windward.net
    Thanks, Brad! :D

    Living Legacy

    unread,
    Apr 5, 2017, 5:53:28 PM4/5/17
    to Google Chrome Developer Tools
    What does it mean if we have no Workers tab?


    On Monday, April 7, 2014 at 9:29:12 AM UTC-4, Vsevolod Vlasov wrote:
    1., 2. Look under the Workers in the Sources panel sidebar. (See the bottom of the attached screenshot)
    3. http://www.html5rocks.com/en/tutorials/developertools/revolutions2013/#toc-workspaces
    On Mon, Apr 7, 2014 at 5:07 PM, <da...@windward.net> wrote:
    Hi;

    How exactly do I:
    1. open it by clicking a link in the workers list in Sources panel sidebar
    2. check a checkbox that makes all workers break on start.
    3. (add a local folder and) map it to the network resources
    I tried to find the first 2 items and could not. I did find how to add a local folder, but could not find how to map it.

    ??? - thanks - dave


    On Monday, April 7, 2014 3:05:27 AM UTC-6, Vsevolod Vlasov wrote:
    Workers debugging could only be done in a separate worker front-end currently. You could open it by clicking a link in the workers list in Sources panel sidebar. You could also check a checkbox that makes all workers break on start.

    As for debugging the scripts that are loaded dynamically you have two options:
    1) Wait until the script is loaded, set the breakpoint and reload the page. the breakpoint will be kept in the VM and debugger will pause on it when needed.
    2) Use DevTools workspaces to add a local folder and map it to the network resources so that the dynamically loaded script file is always available and you could set breakpoint in it.


    On Thu, Apr 3, 2014 at 8:38 PM, <da...@windward.net> wrote:
    Hi;

    The Sources tree does not list all files, just the ones it knows are in use. How can I get other files in there so I can set breakpoints in them before they execute for the first time?

    Also, how do I get worker .js files in the Sources? Generally they don't show and Ctrl-O doesn't list it. (And sometimes they do show up - no idea why when that happens.)


    --
    You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.
    Reply all
    Reply to author
    Forward
    0 new messages