this link worked for me THANK YOU!!!!
Excellent. Release the hounds 🙂
I don't have these issues at all (use of old FF version31, or the fact that I have few purchases, no watchlist, no cancelled purchases, etc, or just dumb luck), and can't test any of this, but from reading the various threads and ruminating on the issue my understanding is:
- eBay changed something that is causing one of the (too many) poorly coded scripts to go either go into a terminal spin loop or just take far too long to execute on purchase history, watchlist, and/or collections list pages when there are a lot of items on the lists and possibly any number > 10 displayed per page
- The official answer for why it's happening appears to be to blame the user's hardware. I'm calling **bleep** on that - you don't roll out code to do a simple thing like display/manipulate a list that requires modern gaming hardware. (not a programmer but have coded for 40 years and know better).
- Whether this issue is going to be addressed and fixed is unknown, but for now it looks like using the link I provided is a workaround.
If the script timeout issue occurs even using the link, keep in mind that that link only addresses the items per page (IPP) for "Orders" on the purchase history page, so even if IPP is set to 10 for orders, it is possible and likely that the scripts can also blow up if there are high numbers of "Canceled Items", Canceled Invoices", and/or "Returns and Canceled Orders", which need to be addressed separately.
(seems unlikely that anyone could have enough of those to choke the script, but just in case...)
────────────────────────────────────────────────────────
Links for the 4 of containers/sections on Purchase History page I see (any of which I believe could cause the script(s) to timeout).
(Don't think a single link can change all 4 IPP numbers in one go, so requires use of 4 separate links if needed):
Load Purchase History page with "Orders" container IPP set to 10
https://www.ebay.com/myb/PurchaseHistory#PurchaseHistoryOrdersContainer?ipp=10&melid=itemspp
Load Purchase History page with "Canceled Items" container IPP set to 10
https://www.ebay.com/myb/PurchaseHistory#PurchaseHistoryCancelCommitsContainer?ipp=10&melid=itemspp
Load Purchase History page with "Returns and Canceled Invoices" container IPP set to 10
https://www.ebay.com/myb/PurchaseHistory#PurchaseHistoryCancelInvoicesContainer?ipp=10&melid=itemspp
Load Purchase History page with "Returns & Canceled Orders" container IPP set to 10
https://www.ebay.com/myb/PurchaseHistory#PurchaseHistoryReturnsContainer?ipp=10&melid=itemspp
────────────────────────────────────────────────────────
If the above link method to access the Purchase History page doesn't work, or you just want to do it the hard way.....
Another approach is if you see the script timeout alert popup, you should be able to allow the script to continue instead of killing it, and wait to see if it ever finishes. Only have to be patient one time to get the page to load and then reduce the items per page to 10 (which seems to be a low enough number that even desktops from 1990 have enough hamster power to allow the script to complete.)
If you don't have the option to continue the script when it is timing out, another option is to extend the JavaScript timeout period in Firefox. Increasing it might give the script enough time to get whatever it is doing done before Firefox slaps it down (once again, that means you have to patiently wait for it to load).
In Firefox 31, I use an old addon called "Control de Scripts" that I've "hacked" to install in FF31 (the last released version only installed in up to FF21). Actually modified it to install in up to FF99, but haven't installed and tested in anything above FF31 to see if actually works. (PM me if you want a copy of the hacked addon xpi) https://addons.mozilla.org/en-US/firefox/addon/controle-de-scripts/
Mine is set to 10 seconds since I don't have issues and don't want to wait normally. I think the out of the box FF default is 30 seconds, and I'm recommending that those with the script timeout issue increase it to 60sec, 120sec, or whatever it takes to get the page to load once.
A final way to do this without a GUI interface via an addon is by modifying the timeout value in Firefox manually through about:config. Open about:config in the address bar, type "dom.max_script_run_time" (no quotes) in the search bar, double click the dom.max_script_run_time setting, change the value in the dialog to 60, 90, 231, etc, and save.
────────────────────────────────────────────────────────
Curious about the hardware aspects of this. If those of you who are/were having an issue with the script timeout could take a minute to post some hardware/OS specs it could be enlightening (interested to see if only "old, slow hardware" is having issues, if "modern" hardware is also having issues, or if it isn't really a hardware issue and old and new are affected.
- Operating System (ie: Windows XP SP3)
- CPU model (ie: Intel Core2 Quad Q9550)
- CPU Speed (ie: 2.83 GHz)
- RAM (ie: 4Gb)
(easily obtained in XP and Win7 by right clicking on My Computer and then Properties, or System Properties in Control Panel, via third part hardware utilities, System Info in Win 10 I think, ...)
