Bug: Logos draining battery on MacBook Pro by requiring High Performance GPU

I purchased a new MacBook Pro last week, moved everything over and noticed my battery was draining faster than my 2009 MacBook Pro even though I was using the exact same programs. Every time I checked the battery icon, I noticed that Logos was listed as "Apps Using Significant Energy."

For example, here is a screenshot. At the time I took this screenshot, I hadn't touched Logos in hours. It was not indexing. It was on a different desktop from the one I was using. I was working on a Numbers spreadsheet and at the same time playing a John Piper sermon on Youtube. With all that going, the only app "using significant energy" was Logos.

I looked around a bit in Activity Monitor to see what the problem was and then I noticed this:

I'm guessing this is why Logos is draining my battery so fast. Logos is the only process running on my computer that, for some reason, is requiring the high performance GPU. Even my playback of a youtube video doesn't require the GPU. My old MacBook Pro only had the integrated GPU so this would explain why Logos 7 wasn't draining the battery as fast on that laptop. However, the new one has an upgraded discreet GPU which apparently Logos is requiring for some reason even though no other app on my laptop is.

It would be awesome if this could be fixed. With Logos even running in the background I can just watch my battery drop and it would really slow my workflow down to have to quit Logos and reopen it constantly just to keep it from running in the background and draining battery...

Find more posts tagged with

Comments

Jonathan Bradley

I don't know all of the details, but I know consumer reports did not give the new MacBook Pros their blessing/highest rating because of a battery life issue. You might want to look that up.

Samuel

https://community.logos.com/discussion/comment/875518#Comment_875518

I don't know all of the details, but I know consumer reports did not give the new MacBook Pros their blessing/highest rating because of a battery life issue. You might want to look that up.

Yes, I'm familiar with that. Most of that was fixed was the latest release of MacOS Sierra. The problem I posted is a problem specific to Logos that's causing Logos to drain the battery very quickly. Without Logos running, I get pretty decent battery life out of the computer.

Philana R. Crouch

I purchased a new MacBook Pro last week, moved everything over and noticed my battery was draining faster than my 2009 MacBook Pro even though I was using the exact same programs. Every time I checked the battery icon, I noticed that Logos was listed as "Apps Using Significant Energy."

For example, here is a screenshot. At the time I took this screenshot, I hadn't touched Logos in hours. It was not indexing. It was on a different desktop from the one I was using. I was working on a Numbers spreadsheet and at the same time playing a John Piper sermon on Youtube. With all that going, the only app "using significant energy" was Logos.

I looked around a bit in Activity Monitor to see what the problem was and then I noticed this:

I'm guessing this is why Logos is draining my battery so fast. Logos is the only process running on my computer that, for some reason, is requiring the high performance GPU. Even my playback of a youtube video doesn't require the GPU. My old MacBook Pro only had the integrated GPU so this would explain why Logos 7 wasn't draining the battery as fast on that laptop. However, the new one has an upgraded discreet GPU which apparently Logos is requiring for some reason even though no other app on my laptop is.

It would be awesome if this could be fixed. With Logos even running in the background I can just watch my battery drop and it would really slow my workflow down to have to quit Logos and reopen it constantly just to keep it from running in the background and draining battery...

Samuel,

Can you reproduce this and upload logs? Also was Logos doing anything in the background (i.e. indexing). What type of tasks were you doing? This will help in trying to see what is going on.

Samuel

https://community.logos.com/discussion/comment/875569#Comment_875569

Samuel,

Can you reproduce this and upload logs? Also was Logos doing anything in the background (i.e. indexing). What type of tasks were you doing? This will help in trying to see what is going on.

I've attached logs files. To reproduce the error:

1. Start Logos 7.

2. Open Activity Manager and check the "energy" tab and you will see that Logos is set to "Requires High Perf GPU"

Logos is requiring the higher performance (and high battery drain) GPU without me even doing anything in Logos.

6521.logos-logs.zip

Samuel

https://community.logos.com/discussion/comment/875671#Comment_875671

I wanted to leave a note for anyone else searching for this issue that I've noticed this week it is resolved. I'm not sure if it was a Logos update, but Logos is no longer requiring the High Performance GPU on my machine and the battery is not draining as fast as a result.

Josh Boldman

https://community.logos.com/discussion/comment/877197#Comment_877197

I'm still having this issue, and I'm using a Late 2013 15" MBP. Any suggestions?

JT (alabama24)

https://community.logos.com/discussion/comment/877454#Comment_877454

I'm still having this issue, and I'm using a Late 2013 15" MBP. Any suggestions?

Please create a new thread and explain your issue clearly, providing appropriate details. Philana asked some questions above which should be helpful in diagnostic:

Can you reproduce this and upload logs? Also was Logos doing anything in the background (i.e. indexing). What type of tasks were you doing? This will help in trying to see what is going on.

Samuel

https://community.logos.com/discussion/comment/877461#Comment_877461

I'm sorry to say this bug is back. I'm on Logos 7.3 SR-3 and Logos is back to requiring the High Performance GPU which causes the battery to drain faster. It's the only application doing this.

John Goodman

https://community.logos.com/discussion/comment/879071#Comment_879071

I'm see the same on my mac. High battery drain from Logos. No indexing while I've been using other apps not logos.

JT (alabama24)

https://community.logos.com/discussion/comment/879071#Comment_879071

I'm sorry to say this bug is back.

Philana will want to see new logs.

Jonathan Bradley

https://community.logos.com/discussion/comment/879077#Comment_879077

I'm sorry to say this bug is back.

Philana will want to see new logs.

My MacBook Pro (early 2015 edition) says it's using significant energy, however, I have not seen a real drain on my battery life. Here are my logs though in case they might help.

8078.LogosLogs.jonathanbradley.20170130-221806.zip

Michael McLane

I can confirm, as I did in another thread on this same issue, that Logos eats through the power on the 2016 MacBook Pro. The 7.4 RC-1 is requiring the discrete, high performance gpu. It cuts my cuts my charge life in half.

John Goodman

https://community.logos.com/discussion/comment/879248#Comment_879248

This might be helpful?

https://developer.apple.com/library/content/qa/qa1734/_index.html

It outlines how to ensure the integrated graphics is used instead of the discreet graphics.

I would certainly appreciate the extra battery life.

Philana R. Crouch

https://community.logos.com/discussion/comment/879248#Comment_879248

Are you doing anything else in Logos, and had you used it a lot that same day. It will stay in the Battery menu even if Logos has been only running in the background for several hours.

When the app is running in the background what is left open? A specific layout or the homepage.

Michael McLane

https://community.logos.com/discussion/comment/879272#Comment_879272

Are you doing anything else in Logos, and had you used it a lot that same day. It will stay in the Battery menu even if Logos has been only running in the background for several hours.

When the app is running in the background where is open to? A specific layout or the homepage.

Here is a link to my comment in another thread on this topic that may answer some of those questions:

http://community.logos.com/forums/p/134435/873609.aspx#873609

Philana R. Crouch

https://community.logos.com/discussion/comment/879274#Comment_879274

Here is a link to my comment in another thread on this topic that may answer some of those questions:

http://community.logos.com/forums/p/134435/873609.aspx#873609

Hi Michael,

Thanks for the added info, we are looking into this.

LimJK

https://community.logos.com/discussion/comment/879285#Comment_879285

Philana,

I raised this issue long time ago in I think in 2011 on Logos 4 when I got my MacBookPro with dual GPU and pointed Logos to information here ... for a while it was OK.

Now When I start with Logos Home page, it will always switch from integrated to discrete graphics mode and stay there until I quit Logos. If I start Logos with a Blank Home Page, it stays on integrated graphics mode. Since I am able to get about 6 hours battery life when I am out of the house ... it is not an acute problem to me. However, if Logos can do something about it, I will be happier [:)]

Michael McLane

https://community.logos.com/discussion/comment/879285#Comment_879285

Thanks for the added info, we are looking into this.

Here are a couple of screen shots that may give the techs some more help with this.

Logos starts in a state of not using the discrete GPU.

It seems that the home page will trigger the discrete GPU as well as the Courses Tool and Media tool. It seems to be related to the LogosCEF.

Guides, Search, Layouts, Course videos, Factbook do not trigger the discrete GPU. When the discrete GPU is not used there is much less battery drain, much less.

The first screen shot shows without using the discrete GPU. The second one shows it enabled.

Stephen Steele

https://community.logos.com/discussion/comment/879611#Comment_879611

I have the same issue with the new Macbook Pro. Logos uses the discrete GPU all the time, no matter what I'm doing.

I initially bought the 13" MBP (non touch-bar, integrated graphics) however returned it as I needed a larger screen size. Battery life was amazing, and Logos performance was great.

However I returned it and bought the 15" version. If there had been one with only integrated graphics, I would have got it.

Sadly however Logos always uses the discrete GPU. Activity Monitor tells you which GPU is in use, and with Logos it's always using 'High Performance'. But as soon as I close Logos it goes back to integrated.

The vast majority of what I do in Logos is read commentaries. I understand the discrete GPU is useful for indexing, but if there was a setting in Logos where users could disable it, I would do it.

Due to this issue I'm getting about half as much battery life as I should be - compared to when it's just using the integrated graphics.

I should note as well that Logos forces use of the discrete GPU even if it's not actively being used, or I'm working on a different workspace etc. I would have expected it to use the 'App Nap' feature which was introduces in Mavericks.

Michael McLane

https://community.logos.com/discussion/comment/879662#Comment_879662

Stephen, are you using 7.4 RC-1? I was having a similar problem that I describe here which sounds like your use case. However, under 7.4 it behaves as I have described above, which isn't ideal but is better.

Michael McLane

https://community.logos.com/discussion/comment/879662#Comment_879662

I understand the discrete GPU is useful for indexing

The discrete GPU is not used by the indexer.

Michael McLane

This is still not fixed in 7.4 RC-1.

Though, I did not really expect it to be fixed so quickly.

But, sooner is better.

Michael McLane

https://community.logos.com/discussion/comment/879611#Comment_879611

Logos starts in a state of not using the discrete GPU.

It seems that the home page will trigger the discrete GPU as well as the Courses Tool and Media tool. It seems to be related to the LogosCEF.

Guides, Search, Layouts, Course videos, Factbook do not trigger the discrete GPU. When the discrete GPU is not used there is much less battery drain, much less.

Text Comparison also seems to trigger the discrete GPU.

Samuel

https://community.logos.com/discussion/comment/879740#Comment_879740

It also looks like using the Media browser switches the app to the high performance GPU

Stephen Steele

https://community.logos.com/discussion/comment/879674#Comment_879674

Stephen, are you using 7.4 RC-1? I was having a similar problem that I describe here which sounds like your use case. However, under 7.4 it behaves as I have described above, which isn't ideal but is better.

I was using 7.3 but am now on 7.4.

For me, it seems that opening 'Text comparison' turns on the discrete GPU.

Also, it seems that once it's on, it's on. Eg if I open 'Text comparison' the gpu changes from 'integrated' to 'high performance', but closing Text Comparison doesn't get it back to 'integrated'. To do that I have to close Logos and re-open it.

Michael McLane

https://community.logos.com/discussion/comment/880524#Comment_880524

Is there any news on this? It is rather cumbersome to have so many of the features of Logos hobble my laptop and drain my battery. If I accidentally open a feature that will cause the GPU to go into overdrive I have to remember it and quit Logos and restart. What a pain! Can we get this fixed? Please?

BTW, I found out the hard way that Sermon Editor activates the high-performance GPU.

Michael

Michael McLane

https://community.logos.com/discussion/comment/891308#Comment_891308

Ooops... add Parallel Gospel Reader.

Michael McLane

https://community.logos.com/discussion/comment/891309#Comment_891309

Is there any news on this? Is there a fix in the pipeline?

Philana R. Crouch

https://community.logos.com/discussion/comment/894016#Comment_894016

Is there any news on this? Is there a fix in the pipeline?

Hi Michaell,

I don't have new info at this time.

Stephen Steele

https://community.logos.com/discussion/comment/894017#Comment_894017

Is there any news on this? Is there a fix in the pipeline?

Hi Michaell,

I don't have new info at this time.

Thanks for your response Philana - but I'm not sure if it gives any more clarity as there wasn't any old info apart from that the issue was being looked into?

It should be an easy fix - as John posted back in January:

This might be helpful?

https://developer.apple.com/library/content/qa/qa1734/_index.html

It outlines how to ensure the integrated graphics is used instead of the discreet graphics.

I would certainly appreciate the extra battery life.

This isn't a niche platform we're talking about - it's Apple's most popular Mac!

Samuel

https://community.logos.com/discussion/comment/894236#Comment_894236

It should be an easy fix - as John posted back in January:

This might be helpful?

https://developer.apple.com/library/content/qa/qa1734/_index.html

It outlines how to ensure the integrated graphics is used instead of the discreet graphics.

The current Logos application already has that setting, so that's why it's apparently not a simple fix. Given how many people use Mac, I would hope that Logos is putting a high priority on this.

You have to remember that Logos isn't really developed for a Mac. It's developed for Windows and then they use Mono software to make it run on a Mac. I can't speak for Logos and I'm not a software developer, but I wouldn't be surprised if the but is somewhere deeper than Logos and probably in the Mono software layer that Logos is using to make what is essentially a windows application run on the Mac.

I dream of a day when Logos rewrites the software to have a Mac native version I bet there would be better performance and it would look a bit better if it used some native Mac controls.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/894256#Comment_894256

I dream of a day when Logos rewrites the software to have a Mac native version I bet there would be better performance and it would look a bit better if it used some native Mac controls.

Thankful for Phil Gons (Faithlife) creating a survey => 10-question survey and thread => How do you use Logos? How can we improve it? where replies could be added with user interface control improvement(s). Also, please elaborate in Phil's thread about performance issues that affect work flow, especially item(s) that interrupt or slow down work flow.

Logos is a resource intensive application on Windows and Mac, which has a shared code base with native graphical user interface code. The shared code base uses .NET Framework on Windows and Microsoft's Mono on Mac. Microsoft purchased Xamarin (and now employs many developers of Mono) => https://www.xamarin.com/microsoft For user interaction, Windows application uses Windows Presentation Foundation (WPF) while Mac application uses native Mac Cocoa coding. Logos user interface is a bit different than Windows and Mac conventions while being easy to switch platforms as desired.

Keep Smiling [:)]

Patrick Lacson

https://community.logos.com/discussion/comment/894510#Comment_894510

I'm getting this on my MacBook Pro 2016 15 w/ touchbar

How can I force Logos to not use high performance GPU?

Randall McRoberts

https://community.logos.com/discussion/comment/896458#Comment_896458

Logos is high-performance software. I find that, on my new MacBook Pro, sometimes it uses HP and sometimes the integrated GP. Sometime it helps to close other apps down. Sometimes it helps to shut down Logos and open it again.

Mostly I'm just resigned to knowing my battery won't last as long when running Logos. I dim and bear it, if you will. It's worth it and I don't expect miracles.

Patrick Lacson

https://community.logos.com/discussion/comment/896463#Comment_896463

Randall, so you're saying there's no way to turn off HP GPU on MacBook Pro for Logos 7? Logos 7 is clearly "high performance", no need to sell that point - I own it .

I just want to turn off dependency on the battery draining hP GPU usage.

Samuel

https://community.logos.com/discussion/comment/896463#Comment_896463

Logos is high-performance software. I find that, on my new MacBook Pro, sometimes it uses HP and sometimes the integrated GP. Sometime it helps to close other apps down. Sometimes it helps to shut down Logos and open it again.

Mostly I'm just resigned to knowing my battery won't last as long when running Logos. I dim and bear it, if you will. It's worth it and I don't expect miracles.

However, this is clearly a Logos bug. The way normal Mac apps work is that they use the high performance GPU when they need it and then switch to the integrated one when they no longer need it. This is they way the Logos app should work, but in Logos' case, once it uses the high performance GPU, it never goes back to the integrated one without restarting Logos. I've just learned if I use any Logos tools I have to restart Logos unless I want my battery drained. The difference in battery performance is pretty significant.

Patrick Lacson

https://community.logos.com/discussion/comment/896474#Comment_896474

yes I took my new MBP to the Genius Bar because the battery drain was so bad. They identified Logos 7 as the culprit. I get 4 hours with Logos 7 running. Without Logos 7 I get 10 hours+

I agree this is totally a bug.

Randall McRoberts

https://community.logos.com/discussion/comment/896479#Comment_896479

I don't see it as a bug. The app works fine. But there is certainly an opportunity for improvement there, and I'd bet they are already working on it.

Samuel

https://community.logos.com/discussion/comment/896538#Comment_896538

I don't see it as a bug. The app works fine. But there is certainly an opportunity for improvement there, and I'd bet they are already working on it.

Not to belabor the point, but it is a bug. Mac applications default to the integrated GPU when the high performance GPU is not needed. Apple added this feature several versions ago to prevent this problem. Logos fails to switch back to the integrated CPU once it uses the high performance GPU for a function. Apple created this functionality to prevent this problem and it is normal for Mac applications to switch between GPUs as needed. Logos is failing to function properly in this respect.

I'm sure they are looking at it and that's why we are all eager for a fix.

Patrick Lacson

https://community.logos.com/discussion/comment/896540#Comment_896540

Does logos have a bug database to look up already discovered issues? Rather than assume they are "working on it" is there a way to know for sure if an upcoming release will fix this bug? (yes it is a bug)

Philana R. Crouch

https://community.logos.com/discussion/comment/899937#Comment_899937

Does logos have a bug database to look up already discovered issues? Rather than assume they are "working on it" is there a way to know for sure if an upcoming release will fix this bug? (yes it is a bug)

Hi Patrick,

We do have a bug case open for this issue.

Patrick Lacson

https://community.logos.com/discussion/comment/899944#Comment_899944

Does logos have a bug database to look up already discovered issues? Rather than assume they are "working on it" is there a way to know for sure if an upcoming release will fix this bug? (yes it is a bug)

Hi Patrick,

We do have a bug case open for this issue.

Thank you, Philana. Is that bug database open to the public so we don't waste time complaining in community forums [:D] Also to help us know when it will be fixed?

Graham Criddle

https://community.logos.com/discussion/comment/900360#Comment_900360

Is that bug database open to the public so we don't waste time complaining in community forums

No this is not shared outside of Faithlife.

Philana R. Crouch

https://community.logos.com/discussion/comment/900360#Comment_900360

Does logos have a bug database to look up already discovered issues? Rather than assume they are "working on it" is there a way to know for sure if an upcoming release will fix this bug? (yes it is a bug)

Hi Patrick,

We do have a bug case open for this issue.

Thank you, Philana. Is that bug database open to the public so we don't waste time complaining in community forums Also to help us know when it will be fixed?

No this is not a public database, we will update this thread and also include an announcement in the release notes. We hope to have a fix available soon.

Philana R. Crouch

It would be awesome if this could be fixed. With Logos even running in the background I can just watch my battery drop and it would really slow my workflow down to have to quit Logos and reopen it constantly just to keep it from running in the background and draining battery...

Samuel, this should be improved in 7.6 SR-1.

Samuel

https://community.logos.com/discussion/comment/903206#Comment_903206

Samuel, this should be improved in 7.6 SR-1.

That's great news - I look forward to the update.

Patrick Lacson

https://community.logos.com/discussion/comment/903206#Comment_903206

I just upgraded to

Logos Bible Software 7.6 SR-1

7.6.0.0037

I still see 'Requires High Perf GPU' in my Activity Monitor for the Logos always set to 'Yes'

LimJK

https://community.logos.com/discussion/comment/903253#Comment_903253

For the time being, this is my workaround:

Do not start Logos with the Home Page, which triggers switch to discrete GPU.

I start with a blank Layout
or Start with a Layouts that do not trigger the GPU switch (I find most of my layouts do not trigger the switch)

Patrick Lacson

https://community.logos.com/discussion/comment/903350#Comment_903350

Thank you LimJK! I reduced my layouts and wow, Logos 7 is finally not use the high performance GPU! Hopefully this will take my new MacBook Pro 2016 beyond 4 hours with Logos running.

Samuel

https://community.logos.com/discussion/comment/903206#Comment_903206

Samuel, this should be improved in 7.6 SR-1.

I just installed the new release and unfortunately it does not seem to be fixed. Just visiting the home page once triggered Logos to use the high powered GPU until I stopped it and restarted it.