How to resolve the issue that “when a *.js larger than 500KB is loaded into the Appeon debugger, the Appeon debugger fails in work.”
Posted by Nico Wang on 17 October 2013 11:16 AM
when you use the Appeon Debugger to debug your application, you may run into the kind of issue like “Appeon Debugger cannot correctly load the JS file since it is over 500KB in size…” as shown below.
This issue is occurring on some of the operation systems such as Windows XP SP3 and Windows Vista, etc. However, during our testing, in Windows XP SP2 and Windows 2003 R2 Standard Edition, the user can debug a *.js file of 2.7MB in an application.
Solution 1: You can perform test on another operation system like Windows XP SP2 if possible.
Solution 2: Restructure code to reduce the size of the application.js and deploy the application in “Debug JS” mode only.
If customer really wants to use the Appeon Debugger, then they would need to restructure their application object so it will reduce the size of the corresponding application.js to be less than 500KB. But before embarking on this task, the customer should first make sure of two things:
1) that the application is deployed in “Debug JS” mode only. They should NOT use “Debug JS/PS” mode with Appeon Debugger, as this will make the file size bigger.
2) they should check to see if any other .JS files are over 500KB (simply browse the Web root folder and sort by file size). In most cases, the only file that should be over 500KB is the application.js.