You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the analyzed file is relatively large, a lot of data is generated. When the browser is used to access and view, the one-time loading of data is too much, which often leads to the browser not responding. Can this problem be optimized?
The text was updated successfully, but these errors were encountered:
👋 @xiaoliusec
Issues is only for reporting a bug/feature request. For limited support, questions, and discussions, please join MobSF Slack channel
Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.
This is because a large amount of data is loaded at one time, especially when some APKs have a lot of strings. Some large applications will have more than 6M of string information, which will cause the browser to load too much data at once and freeze. , I have also discovered this problem before, and it seems that it will not be improved in the short term.
At some point we want to move out from the current way of rendering the whole data to HTML to use something like ReactJS and the MobSF REST APIs. But that would take time. I will track this separately.
When the analyzed file is relatively large, a lot of data is generated. When the browser is used to access and view, the one-time loading of data is too much, which often leads to the browser not responding. Can this problem be optimized?
The text was updated successfully, but these errors were encountered: