creativepackfz / risegadgets

Automatically exported from code.google.com/p/risegadgets
0 stars 0 forks source link

When there are 2 Presentations in the Schedule, and the Photo Album Gadget is in one of those Presentations, sometimes a single image will stay onscreen while the others overlap it. #795

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Add 2 Presentations to a Schedule, one should have the Photo Album Gadget.
2. Notice that at random times for a short random amount of time, the Photo 
Album Gadget will overlap the images, so you will see a single image underneath 
all the other images. This will eventually correct itself. 

For further clarification: http://screencast.com/t/HtiwriIlk

What is the expected output? What do you see instead?
You should never see overlaps with the Photo Album Gadget.

Original issue reported on code.google.com by robb.pr...@risevision.com on 28 Nov 2012 at 1:29

GoogleCodeExporter commented 9 years ago

Original comment by robb.pr...@risevision.com on 28 Nov 2012 at 1:47

GoogleCodeExporter commented 9 years ago
Here's the Schedule, to add your display to, that runs the mix:
http://rvauser.appspot.com/#SCHEDULE_MANAGE/id=74fba25e-3aa5-4746-b2f5-b866d9bb8
cab/company=fee1f642-cdd1-4bc4-8f93-1fc97cb00d55

Note: This issue is easy to reproduce on Windows 7 and Ubuntu 12.04 displays, 
but it’s relatively rare on displays running Ubuntu 12.10.

Original comment by mark.kre...@risevision.com on 30 Nov 2012 at 10:41

GoogleCodeExporter commented 9 years ago

Original comment by donnapep@gmail.com on 6 Dec 2012 at 7:31

GoogleCodeExporter commented 9 years ago

Original comment by mark.kre...@risevision.com on 10 Dec 2012 at 4:38

GoogleCodeExporter commented 9 years ago
As per Mark: It didn't crash the Presentation and there were still no double 
images spotted, however the fixed version of the Gadget seems to consume more 
memory than the previous one. This means that much weaker machines or machines 
that are not set up to restart every 24 hours may get the "Low on Memory" error 
onscreen, or Chrome/Chromium may crash.

For now, we are changing the status of this bug to OnHold and NOT deploying the 
fix to production so we can investigate the memory issue at a later time.

Original comment by robb.pr...@risevision.com on 11 Dec 2012 at 3:12

GoogleCodeExporter commented 9 years ago
Marking this issue as invalid, as the memory on the uptime Displays has been 
running as expected.

Original comment by robb.pr...@risevision.com on 25 Feb 2013 at 1:43