Opened 10 years ago

Last modified 8 years ago

#2578 assigned defect

Story Builder 15 uses 100% of the cpu all time

Reported by: carrott Owned by: RafaelOrtiz
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: StoryBuilder Version: Unspecified
Severity: Unspecified Keywords: sugar-love
Cc: Distribution/OS: Unspecified
Bug Status: New

Description

On XO-1.5 running Build 861 10.1.3-au2
Start Story Builder
Start terminal
Run top
Observe 100% cpu consumption by Story Builder

This is bad because it will consume the battery faster while the laptop is awake and prevent the laptop going to sleep.

Change History (8)

comment:1 Changed 10 years ago by alsroot

  • Bug Status changed from Unconfirmed to Needinfo

In fact, it is how games work. They all time do something, e.g., play animations...

Does v15 have more cpu consumption for you than previous versions?

comment:2 Changed 10 years ago by alsroot

  • Bug Status changed from Needinfo to New
  • Keywords sugar-love added

Hmm.. I found that it doesn't stop processing on the switch to another activity.

I'm setting to keyword to "sugar-love".
Would be useful to stop processing pygame loop on if activity is inactive.

comment:3 Changed 10 years ago by carrott

100% cpu to do nothing doesn't seem like best practice. There are no animations, it's just sitting there doing nothing.

comment:4 Changed 10 years ago by RafaelOrtiz

  • Owner changed from alsroot to RafaelOrtiz
  • Status changed from new to assigned

We need to compare to older versions and other pygame based activities and see what can be do to relief cpu,
previous versions of history builder run fine iirc.

some pygame mod should be involved.

comment:5 Changed 10 years ago by RafaelOrtiz

Gary, has made imporvements to overall pygame performance, worth take a look.

comment:6 follow-up: Changed 10 years ago by RafaelOrtiz

I've also drop down FPS to 20 in order that animations run faster.

comment:7 in reply to: ↑ 6 Changed 10 years ago by RafaelOrtiz

Replying to RafaelOrtiz:

I've also drop down FPS to 20 in order that animations run faster.

This is on latest version on ASLO, the crucial error to tackle is the aforementioned by alsroot.

Note: See TracTickets for help on using tickets.