Android app runs very slowly after resuming from breakpoint










3















My Android app runs dead slow after resuming from a breakpoint, even if I disconnect from the debugger or even unplug the USB cable. I get the same behavior on every device and emulator I've tried. Performance is great until it hits the first breakpoint, but it's unusable after I resume and I have to kill it. It's very frustrating.



It used to work great but it started with Android Studio 3.1.x and it's still happening after I upgraded to 3.2.1, the latest stable release at this time. None of my colleagues who work on the same app have this problem so it's probably not the code. I suspect I have a configuration issue somewhere.



I have no idea what changed when it started. It happens no matter where the breakpoint is. I don't see any errors in LogCat.



I'm using a MacBook Pro (15-inch, 2017) running OSX 10.13.6, Android Studio 3.2.1 and a Pixel XL running P.



Any ideas or suggestions are much appreciated.



UPDATE: It happens on Java breakpoints but not Kotlin.










share|improve this question
























  • Which MacBook Pro?

    – TheWanderer
    Nov 14 '18 at 1:04











  • MacBook Pro (15-inch, 2017)

    – Barry Fruitman
    Nov 14 '18 at 1:06











  • @BarryFruitman Did you ever find the cause of this? I experience the exact same thing, also on a MacBook Pro though mine is 2015.

    – pdub
    Jan 3 at 19:00















3















My Android app runs dead slow after resuming from a breakpoint, even if I disconnect from the debugger or even unplug the USB cable. I get the same behavior on every device and emulator I've tried. Performance is great until it hits the first breakpoint, but it's unusable after I resume and I have to kill it. It's very frustrating.



It used to work great but it started with Android Studio 3.1.x and it's still happening after I upgraded to 3.2.1, the latest stable release at this time. None of my colleagues who work on the same app have this problem so it's probably not the code. I suspect I have a configuration issue somewhere.



I have no idea what changed when it started. It happens no matter where the breakpoint is. I don't see any errors in LogCat.



I'm using a MacBook Pro (15-inch, 2017) running OSX 10.13.6, Android Studio 3.2.1 and a Pixel XL running P.



Any ideas or suggestions are much appreciated.



UPDATE: It happens on Java breakpoints but not Kotlin.










share|improve this question
























  • Which MacBook Pro?

    – TheWanderer
    Nov 14 '18 at 1:04











  • MacBook Pro (15-inch, 2017)

    – Barry Fruitman
    Nov 14 '18 at 1:06











  • @BarryFruitman Did you ever find the cause of this? I experience the exact same thing, also on a MacBook Pro though mine is 2015.

    – pdub
    Jan 3 at 19:00













3












3








3








My Android app runs dead slow after resuming from a breakpoint, even if I disconnect from the debugger or even unplug the USB cable. I get the same behavior on every device and emulator I've tried. Performance is great until it hits the first breakpoint, but it's unusable after I resume and I have to kill it. It's very frustrating.



It used to work great but it started with Android Studio 3.1.x and it's still happening after I upgraded to 3.2.1, the latest stable release at this time. None of my colleagues who work on the same app have this problem so it's probably not the code. I suspect I have a configuration issue somewhere.



I have no idea what changed when it started. It happens no matter where the breakpoint is. I don't see any errors in LogCat.



I'm using a MacBook Pro (15-inch, 2017) running OSX 10.13.6, Android Studio 3.2.1 and a Pixel XL running P.



Any ideas or suggestions are much appreciated.



UPDATE: It happens on Java breakpoints but not Kotlin.










share|improve this question
















My Android app runs dead slow after resuming from a breakpoint, even if I disconnect from the debugger or even unplug the USB cable. I get the same behavior on every device and emulator I've tried. Performance is great until it hits the first breakpoint, but it's unusable after I resume and I have to kill it. It's very frustrating.



It used to work great but it started with Android Studio 3.1.x and it's still happening after I upgraded to 3.2.1, the latest stable release at this time. None of my colleagues who work on the same app have this problem so it's probably not the code. I suspect I have a configuration issue somewhere.



I have no idea what changed when it started. It happens no matter where the breakpoint is. I don't see any errors in LogCat.



I'm using a MacBook Pro (15-inch, 2017) running OSX 10.13.6, Android Studio 3.2.1 and a Pixel XL running P.



Any ideas or suggestions are much appreciated.



UPDATE: It happens on Java breakpoints but not Kotlin.







android android-studio android-debug android-studio-3.2






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 14 '18 at 22:28







Barry Fruitman

















asked Nov 14 '18 at 1:04









Barry FruitmanBarry Fruitman

6,6941051106




6,6941051106












  • Which MacBook Pro?

    – TheWanderer
    Nov 14 '18 at 1:04











  • MacBook Pro (15-inch, 2017)

    – Barry Fruitman
    Nov 14 '18 at 1:06











  • @BarryFruitman Did you ever find the cause of this? I experience the exact same thing, also on a MacBook Pro though mine is 2015.

    – pdub
    Jan 3 at 19:00

















  • Which MacBook Pro?

    – TheWanderer
    Nov 14 '18 at 1:04











  • MacBook Pro (15-inch, 2017)

    – Barry Fruitman
    Nov 14 '18 at 1:06











  • @BarryFruitman Did you ever find the cause of this? I experience the exact same thing, also on a MacBook Pro though mine is 2015.

    – pdub
    Jan 3 at 19:00
















Which MacBook Pro?

– TheWanderer
Nov 14 '18 at 1:04





Which MacBook Pro?

– TheWanderer
Nov 14 '18 at 1:04













MacBook Pro (15-inch, 2017)

– Barry Fruitman
Nov 14 '18 at 1:06





MacBook Pro (15-inch, 2017)

– Barry Fruitman
Nov 14 '18 at 1:06













@BarryFruitman Did you ever find the cause of this? I experience the exact same thing, also on a MacBook Pro though mine is 2015.

– pdub
Jan 3 at 19:00





@BarryFruitman Did you ever find the cause of this? I experience the exact same thing, also on a MacBook Pro though mine is 2015.

– pdub
Jan 3 at 19:00












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53291729%2fandroid-app-runs-very-slowly-after-resuming-from-breakpoint%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53291729%2fandroid-app-runs-very-slowly-after-resuming-from-breakpoint%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to how show current date and time by default on contact form 7 in WordPress without taking input from user in datetimepicker

Syphilis

Darth Vader #20