Known Issues & Limitations
If you can't solve the issue here, you might want to visit the WASP Support site where you will be able to look for additional feedback provided by other WASP users.
Detection
- Tab switching/Open in tab/page loading
- If you do "right-click Open Link in New Tab" or switch tab before the page is fully loaded the WASP sidebar won't get updated correctly.
If you want to see accurate data, you must let the page load completely.
- WASP initialization
- Tabs opened before WASP was loaded are not processed, except the most current
one.
Bugs
- Memory leak
- In some cases, when a popup window is open and closed, WASP is indirectly causing a memory leak. This is a Firefox 2.x bug fixed in Firefox 3.x.
Crawling
- Crawl wait
- When crawling, WASP will wait if a dialog is open (prompt for username/password on secured site, alert, Flash install, etc.).
Simply answer or close the dialog to continue.
- Crawl hang
- Sometimes a page never stops loading (typically because of a badly performing page).
Simply click the "stop" button and WASP will skip to the next link in the crawl list.
- Crawl performance
- Crawling is a CPU/memory/network intensive task. When crawling, all other applications and extensions should be stoped/disabled to speed up the process and free as much resources as possible.
