Basically a FireFox portable installation on the C: drive, latest updates. Running debugger cannot set breakpoints. It breaks at the timer when any breakpoint is set. There have been times when I beat it to a breakpoint but have not identified how I did it. Any changes and reload of the page/script and we are back to square one anyway.
I have FF portable 34.05 on an eSATAp external which I keep because that will debug my script. Script is 25K in a .js file with a second file that sets some variables, one array is a lexicon (encoded to reduce bulk), the current size is 80K. Lenovo T410s, Win7 Pro.
Any ideas anyone?
Short of fudging the timer and manually forwarding time, I have no workaround. Given the logistics it could get confusing and error prone.
I could uninstall and load regular FF, but suspect it would make no difference - what does the forum think?
"I have FF portable 34.05 on an eSATAp external which I keep because that will debug my script. Script is 25K in a .js file with a second file that sets some variables, one array is a lexicon (encoded to reduce bulk), the current size is 80K. Lenovo T410s, Win7 Pro."
Current version of FF is 43.0.2
“Be who you are and say what you feel because those who mind don't matter and those who matter don't mind.” Dr. Seuss
current version does not allow for any realistic debugging as outlined in OP. timer refers.
Version 34.05 does. Hence its preservation & use. Successfully for debugging. Alternative would be IE11 &/or Chrome!
re-statement of principle question: "FF portable on C: drive, is it liable to anomalies?"
And as there are peeps out there still using IE8 and who knows what FF versions. It is not exactly good practice to test only on the latest equipment.
I don't subscribe to the philosophy "It works on my machine!!!"
I guess the forum doesn't think.
Latest FF Portable no different.
Hello Chrome.
!
you tried entering Firefox tools and then developer tools? I use the debugger there often.
“Be who you are and say what you feel because those who mind don't matter and those who matter don't mind.” Dr. Seuss
Can't see any other way to invoke the debugger. So yes, all the time.
After the last update FF 65.0.1 (portable) it won't even break on any breakpoints set.
Win 7 32 bit.
Not C: drive - so used as a portable browser. If is was paid-for I would not be as relaxed about the situation.
I only have time to briefly skim the thread so haven't read everything in detail, so apologies if you have already tried this, but I would suggest trying a fresh install of FF portable and check if it has the same issues.
Sometimes profile "crumbs" can get left around as you upgrade (not something we can really handle) that may cause problems.