Closed GoogleCodeExporter closed 9 years ago
Unfortunately, that is not enough information to go on to fix anything, as I
don't get that behavior on my
machine at all.
If you can narrow it down to something more specific, that would help a lot.
Original comment by paracel...@gmail.com
on 29 Nov 2009 at 11:22
I went back to 2.0 after posting this. But then I read your response,
re-downloaded
the binary to snoop some more (I always wanted a good reason to use Shark....),
and
it seems so much happier now. I fear some corruption must have been involved
with the
first one. Thanks for looking into this anyway.
Original comment by karl.ha...@gmail.com
on 30 Nov 2009 at 2:39
I got it to come back. Or, at least I managed to make a similiar behavior come
back.
Some more background: there are about 2700 photos in this directory.
The hickup seems to be related to deleting an image. If I press command-delete
to
move the current image to the trash, Xee loads the next image in the sequence
and
shows it to me, however it will then pinwheel if I try to go back one in the
sequence. These pauses are about 30 seconds long.
I'm not sure this is my original problem... I'm sure i was just browsing the
images
as quickly as they could be loaded.
I'm not clued in enough to be sure this is the right idea, but I have Shark Time
Profiles for this (3 of them) that seem to indicate that Xee is rebuilding and
sorting a list of files in the directory when this happens. I could send these
to you
if you'd like.
Original comment by karl.ha...@gmail.com
on 30 Nov 2009 at 3:58
You can post them as an attachment here. They might be useful. I'll see if I
can recreate
that too when I get back to working on Xee.
Original comment by paracel...@gmail.com
on 30 Nov 2009 at 11:32
Here's the Shark traces I referred to
Thanks again!
Original comment by karl.ha...@gmail.com
on 1 Dec 2009 at 2:14
Attachments:
I got a little more time to experiment. I think the problem is related to the
number
of files in the directory. In a directory with fewer images in it (~20 in this
case)
I can delete files and then load the next or previous image without much pause.
Going
back to the thousands-of-files directory, the problem returns.
Original comment by karl.ha...@gmail.com
on 12 Dec 2009 at 3:35
I think I finally managed to recreate this, too. I'll be looking into it.
Original comment by paracel...@gmail.com
on 13 Dec 2009 at 3:36
Turns out it was pretty simple once I could reproduce it. For some reason,
testing if an
FSRef is valid is *really* slow, but the code should work without doing that,
too, so I just
removed the check.
Well, hopefully it works right. It's a lot faster, at least.
Original comment by paracel...@gmail.com
on 13 Dec 2009 at 4:10
Original issue reported on code.google.com by
karl.ha...@gmail.com
on 29 Nov 2009 at 6:37