Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Performance dropped in latest version of BurpSuite? (MacOS)

Daniel | Last updated: May 13, 2017 06:08AM UTC

Hi! Since the latest version of BurpSuite (1.7.22) I noticed quite some drop in performance on MacOS. I mainly use FireFox (also latest version) to browse. I often see that pages are loaded really slow (or don't load at all), until I "activate" Burp again. With "Activate" I mean that I need to click on the Burp icon in the Dock. It feels like Burp pauses until I make the window visible again. Any clue? Please let me know if you need additional information.

Liam, PortSwigger Agent | Last updated: May 15, 2017 10:17AM UTC

Hi Daniel Thanks for your message. We've just tested the latest version of Burp Suite with Firefox and Sarafi on OS X EL Capitan 10.11.2. Are you using the the JAR file or the EXE version of Burp? Which OS version are you using?

Burp User | Last updated: May 18, 2017 08:46PM UTC

May not be the same issue, but I'm occasionally experiencing heavy cpu usage during scans with 1.7.22 as well (Win7 64 bit and Debian Jessie). When the scan ends, the cpu usage drops to normal. Unfortunately, this is not a reproducible phenomenon. I'm using the plain JAR file, java version is jre1.8.0_131 in both operating systems.

Burp User | Last updated: May 18, 2017 09:18PM UTC

Okay, the issue I mentioned may not be an issue. I suspect it is caused by a large (~200 kb) javascript file. Sorry for crying wolf.

Liam, PortSwigger Agent | Last updated: May 19, 2017 09:06AM UTC

Hi Daniel Are you still experiencing Burp appearing to stop traffic when the application is minimized? Are you sure you aren't closing Burp? Is this happening on a single application or across a range of sites?

Burp User | Last updated: May 22, 2017 02:37PM UTC

Sorry for the slow response. I'm using the exe version of Burp

Burp User | Last updated: May 22, 2017 02:37PM UTC

And I'm also on OS X EL Capitan 10.11.2

Burp User | Last updated: May 22, 2017 07:37PM UTC

I'm sure application keeps on running. Traffic continues when I maximize it again. I have the feeling that it happens for all sites (so not dependent on what I have in scope)

PortSwigger Agent | Last updated: May 23, 2017 09:17AM UTC

We're not able to reproduce any issue where Burp stops processing traffic when the window is minimized. Are you saying that you have Proxy interception disabled, and everything is working ok in your browser, and when you minimize Burp then the browser stops being able to load anything?

Burp User | Last updated: May 24, 2017 04:15PM UTC

Yes, but not always. Once I've maximized the window again, everything starts working fine for some time. Later (not predictable, sometimes a few minutes, sometimes an hour) it stops working again. I'm on java version 1.8.0_112-b16 Proxy interception is disabled. Mostly I have some hostnames "in scope" and I disable logging of out-of-scope hosts.

PortSwigger Agent | Last updated: May 25, 2017 07:47AM UTC

Thanks for confirming. This is certainly unexpected behavior. When you observe the problem, if you open the MacOS Activity Monitor, do you see any CPU activity for Burp? Is it possible that your OS has somehow suspended the process after it has run in the background for a while?

Burp User | Last updated: Jul 11, 2017 10:24AM UTC

I believe this problem is caused by MacOS App Nap. I was experiencing this same issue and I noticed that when Burp Suite was not in focus or behind other windows it would go into App Nap (noticed in Activity Monitor). In MacOS Sierra you can no longer change the App Nap settings in Finder per application and Apple expects the developer to make the application App Nap aware. As a work around you can either disable App Nap system wide or use a script to disable it per app. Here is the aforementioned script: https://gist.github.com/algb12/74535fccfb528fae1d7a So far it's really helped the responsive of Burp and the proxy functionality on my system.

PortSwigger Agent | Last updated: Jul 11, 2017 10:25AM UTC

Just to let you know we've fixed this issue in today's release (1.7.27). Thanks again for your feedback and please let us know if you run into any other problems.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.