bearrundr / movist

Automatically exported from code.google.com/p/movist
GNU General Public License v3.0
0 stars 0 forks source link

repeated crashes on Snow Leopard after idle #83

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
WHAT STEPS WILL REPRODUCE THE PROBLEM?

1. Play videos in Movist
2. Pause videos
3. Leave the computer alone for a while, let the screen-saver kick in
4. Return and see that Movist has crashed

WHAT IS THE EXPECTED OUTPUT? WHAT DO YOU SEE INSTEAD?

Expected output is for Movist to still be there when i return. :(

What i see instead: Movist 'unexpectedly quit'

WHAT VERSION OF THE PRODUCT ARE YOU USING? ON WHAT OPERATING SYSTEM?

Movist version 0.6.4
OS version 10.6.0 / 10.6.1

PLEASE PROVIDE ANY ADDITIONAL INFORMATION BELOW.

This started happening after i installed Snow Leopard (it NEVER occurred on
Leopard, even with the same exact video files). This was a clean install of
both Snow Leopard and Movist, so i don't think it's a preferences issue. So
far it's been a couple of times, and each time it's always occurred
immediately after bringing the computer back from the screen-saver.

For example, two or three times it's happened when i was watching a video
before bed, then paused and went to sleep. When i woke up (6 to 10 hours
later, depending on what day it was) and brought the computer display back
on Movist had crashed.

It also happened just now after i returned to the kitchen from making food
(which took maybe an hour). As soon as i came back, again, Movist crashed.

This has NOT happened to me yet when Movist was actually in use. Only when
it's been idle for a while.

Attached are the two most recent crash logs.

Original issue reported on code.google.com by okd...@gmail.com on 11 Sep 2009 at 10:26

Attachments:

GoogleCodeExporter commented 9 years ago
Similar here. I left the video play back paused and went to make a drink. Hit 
the
space bar to start playing again, and my MacBook Restarted. No crash, no 
warning.
Posted here, because it was after a lengthy pause similar to the original bug.

Other than that I like it

Original comment by jezza.ro...@gmail.com on 27 Feb 2010 at 2:40