Closed GoogleCodeExporter closed 9 years ago
I have seen some vague reports of this before, but I can't quite figure out
what causes it. Can you tell me what hardware you are using?
Also, do you have a chance to upgrade to 10.8?
Original comment by paracel...@gmail.com
on 9 Oct 2013 at 8:50
macbook pro 13" early 2011, 8Gb ram
sincerely i have no plan to buy 10.8....
i have done more tests, seems that the freeze occurs after few moments from
opening the image. i can scroll various images when suddenly (after 3, 4, 5
sec) the image on full screen disappear, i see the desktop and i can move just
the cursor (that is unable to click). also cmd+alt+esc does nothing, i must to
force the shut down.
i'm thinking that issue is correlate to full screen view.
ideas?
Original comment by diego.ba...@gmail.com
on 9 Oct 2013 at 9:14
ok i can reproduce better the crash.
i insert a usb flash drive (ntfs 12gb);
if i view the photos all goes well, even if i watch them full screen.
but, if i toggle under preference "immediatly switch to full screen" with the
1st photos come the crash.
with an old version of xee (maybe 2.2 not sure) all was ok.
Original comment by diego.ba...@gmail.com
on 10 Oct 2013 at 3:50
Funny, does it only happen with the USB drive, or also from the regular drive?
Original comment by paracel...@gmail.com
on 10 Oct 2013 at 4:53
also from regular drive.
Original comment by diego.ba...@gmail.com
on 10 Oct 2013 at 9:37
Very weird.
Well, basically, this is an OS X bug. It should be impossible for any program
to freeze the computer like that, and if it happens, then OS X is not doing its
job right. In practice, it is probably some kind of driver bug.
But since it's in 10.7, the odds of Apple bothering to do anything about it are
very small. And since I can't reproduce it, I can't figure out a way to work
around it. So I am sort of stuck.
Original comment by paracel...@gmail.com
on 10 Oct 2013 at 10:11
I've downloaded the 3.0.1 from older files, all work fine with this, and the
loading time between photos are also really short in comparison to latest
release.
Original comment by diego.ba...@gmail.com
on 12 Oct 2013 at 4:49
Issue 379 has been merged into this issue.
Original comment by paracel...@gmail.com
on 12 Oct 2013 at 9:17
That's weird, I can't think of much that has changed between those versions.
Original comment by paracel...@gmail.com
on 12 Oct 2013 at 9:18
Issue 368 has been merged into this issue.
Original comment by paracel...@gmail.com
on 12 Oct 2013 at 9:27
here just to say that version 3.1 with osx Mavericks works finally fine!
upgraded, tested and no freeze or crash happened.
Original comment by diego.ba...@gmail.com
on 25 Oct 2013 at 7:24
Yeah, I suspect it is triggering a driver bug that only exists on 10.7.
Original comment by paracel...@gmail.com
on 25 Oct 2013 at 7:26
I am also using Xee 3.1 on OSX 10.7.5 and experiencing so many freezes I'm back
to using Xee 2. When the app freezes, it locks the entire computer, requiring
shutdown via the power button. I have no idea when/if I will install
Mavericks, but this is very disturbing behavior. I can't believe I paid for
the app only to be unable to run it. Perhaps you should specify it only runs
on Mavericks. I was using version 2 for several years without any issues.
Original comment by mareic...@gmail.com
on 8 Nov 2013 at 1:00
Could somebody who has had this problem, and is still on 10.7, check if
https://xee.googlecode.com/files/Xee3.3beta1.zip works any better?
Note: This is beta, and has another bug on 10.7 where it might render images
upside-down, but ignore that. Just want to know if it crashes or not.
(I finally found a 10.7 machine that doesn't crash but had weird visual bugs on
the loading animation. I fixed those, and I wonder if that was also causing the
crashes.)
Original comment by paracel...@gmail.com
on 13 Nov 2013 at 9:59
I will test it out and let you know if I encounter freezes.
Original comment by mareic...@gmail.com
on 14 Nov 2013 at 2:24
Any luck? 3.3 is almost ready for release, so it'd be nice to know if this
happened to get fixed too.
Original comment by paracel...@gmail.com
on 14 Nov 2013 at 11:07
[deleted comment]
I've tried it on my MacBook Pro13 late 2011 with 10.7.5 OS X. Finally Xee
doesn't freeze osx. But images are cutted and sometimes reversed.
Original comment by minako...@gmail.com
on 14 Nov 2013 at 11:29
Excellent! The reversed and cut-up images are normal, that's another bug that
should be fixed already. 3.3 should work fine, then. It will be out soon.
Original comment by paracel...@gmail.com
on 14 Nov 2013 at 11:41
3.3 is out now. It should hopefully neither crash nor mess up images.
Original comment by paracel...@gmail.com
on 14 Nov 2013 at 4:23
[deleted comment]
3.3 is out where? I don't see it at
https://code.google.com/p/xee/downloads/list or at the Mac App store.
Original comment by mareic...@gmail.com
on 14 Nov 2013 at 6:45
http://xee.c3.cx/
Original comment by paracel...@gmail.com
on 14 Nov 2013 at 6:57
So I need to download the trial version to v3.3? I already bought the
registered version of v3.
Original comment by mareic...@gmail.com
on 14 Nov 2013 at 7:33
If you bought it from Paddle.com, the trial will work as a full version. If you
bought it from the App Store, you will have to wait until Apple feels like
releasing the update.
Original comment by paracel...@gmail.com
on 14 Nov 2013 at 7:34
ehm downloaded, put in application and "is damaged and can’t be opened. you
should move it to the trash"
Original comment by diego.ba...@gmail.com
on 14 Nov 2013 at 7:46
Seems to be some kind of weird OS X issue with quarantine bits and code
signing... Not sure why, but it works if I upload it as a DMG instead of Zip.
Try re-downloading now.
Original comment by paracel...@gmail.com
on 14 Nov 2013 at 9:56
dmg works fine!
(in Mavericks)
Original comment by diego.ba...@gmail.com
on 14 Nov 2013 at 10:09
Weeeeeird. Going to blame this on some kind of Mavericks bug. Maybe it will get
fixed and I can go back to zip, which I prefer. Anyway, good to know it works!
Original comment by paracel...@gmail.com
on 14 Nov 2013 at 10:17
Original issue reported on code.google.com by
diego.ba...@gmail.com
on 9 Oct 2013 at 4:54