Thanks to both! On Tuesday, July 31, 2012 3:29:32 AM UTC-3, Patrick wrote: > > For all those following this thread, I have since located and fixed the > bug. Quicksilver was trying to read the whole file into memory. The > solution was to just read the first few bytes into memory and test those > accordingly. > > See https://github.com/quicksilver/Quicksilver/pull/1026 > > On 31 July 2012 06:06, Daniel <[email protected]> wrote: > >> A couple thoughts: >> >> Can you try to figure out exactly when it happens? If you have maybe >> 20-50GB *usable* free space (i.e. 30-75GB actually free), get a whole >> bunch of really large files together and go through them in turn, and then >> restart QS or the whole computer and do it in a different order—try to >> really nail down exactly when it happens. I had written a whole bunch more >> here, but the more I think about it from what you said, the answer is >> likely to be…: >> >> ..."always" (i.e. any file with no extension gets loaded into memory, >> which is a problem for big ones. btw try it with "small" files, like >> 100MB—make sure you have free RAM, open up Activity Monitor and watch QS' >> memory usage when browsing to such a file—should jump by exactly the size >> of the file if I'm right). And aHA, in that case it still might have >> something to do with QuickLook, sort of, although it'd be a kind of weird >> bug. You said a 1.6GB movie with its extension removed caused the same >> issue, only you have enough RAM that it topped out before you killed it? >> Now try that same movie *with* the extension—works, right? (Fancy >> preview and everything.) >> >> If so, QS must be *somehow* deciding that when it sees a file with no >> associated QuickLook plugin/extension (not sure which), it's going to load >> the whole thing into memory for some reason. (Actually, try renaming your >> movie file to something.thisisamovie, i.e. a bogus extension, and see if it >> does it then—that'd nail down whether it's based on >> QuickLook/LaunchServices/etc bindings, or on the extension itself). *Why*, >> and therefore where in the code the bug is, I have no idea. >> >> If the answer *isn't* "always", well, then it depends on what the answer >> is :). >> >> ---- >> >> Second thought: I can tell you that this is almost undoubtedly a B69+Snow >> Leopard bug. It doesn't happen with B69/Mountain Lion. Actually, >> thought—try running B69 in 32-bit mode: http://imgur.com/9XgYf. This is >> shotgun debugging, here, but if it has something to do with (a) a 32-bit >> kernel + 64-bit QS (shouldn't be, but never say never), or just a Snow >> Leopard bug that somehow interacts…well, shotgun debugging, as I say. >> Knowing more about when this happens, if the answer isn't "always", would >> be a big help here. >> >> For our sake it'd be nice if you went through with all this, so the bug >> can get fixed for other SL users—but from your post above I can tell that >> you have almost definitely 8GB+ of RAM, so once we figure the bug out you >> could also just upgrade to Mountain Lion and be done with it (I wouldn't go >> near Lion let alone ML on a machine with 4GB, my previous machine had 3 and >> that was barely enough for SL). Also, if the bug still appears, that would >> tell us yet something else. I just recently said "okay this is dumb I'm >> tired of waiting" and went through with the upgrade and haven't had any >> problems yet, despite a good deal of mucking with the system in the past. >> Developers in general have been really good about updates, I haven't even >> had to set Gatekeeper to "All applications" yet. >> >> ---- >> >> Oh, last thought: the first thing I should have said is, "reset" QS ( >> http://qsapp.com/wiki/FAQ#How_to_Quickly_Reset_Quicksilver_Settings) and >> see. If it's a plugin, go through them half at a time—which one it is will >> tell us a ton. Check if it happens for all files first, but then at least >> check *if* resetting fixes it, even if you don't want to go through the >> bisect process with a ton of plugins. >> >> On Monday, July 30, 2012 1:34:59 PM UTC-4, koro wrote: >>> >>> Just an addendum: >>> 1) My OS is Snow Leopard (up to date) >>> 2) This did NOT happen with QS 68, it started when I updated to version >>> 69. >>> >>> >>> On Monday, July 30, 2012 2:30:49 PM UTC-3, koro wrote: >>>> >>>> I don't think this has to do with truecrypt actually. In the first >>>> message I said I thought this only happened with this file, but I was >>>> wrong. >>>> The latest file I tested it on (a 10 GB file) was not a truecrypt file >>>> (it was a virtualbox virtual machine file). I also detected the same >>>> problem with a 1.6 gb file which was a movie file (of course, after >>>> removing its extension), however the latter only causes a momentary >>>> hang >>>> (it actually loads the file to RAM for some reason, as i mentioned in >>>> the previous message). >>>> >>>> On 7/30/12 2:03 PM, Patrick Robertson wrote: >>>> > Thanks koro for all your info, >>>> > >>>> > I haven't seen those log messages before, an interesting one. I'll >>>> keep >>>> > an eye out. >>>> > >>>> > So it appears that this is only happening for TrueCrypt files with no >>>> > extension, yes? I believe what Daniel has said may on the right >>>> lines. I >>>> > will make my own 'large' true crypt file and see how things go. >>>> > >>>> > >>>> > On 30 July 2012 16:17, koro <[email protected] >>>> > <mailto:[email protected]>> wrote: >>>> > >>>> > Thanks to both for the interest. >>>> > >>>> > Quicklook doesn't seem to be the issue (I can quicklook the file >>>> in >>>> > finder just find; it has no associated plugin so it just shows >>>> the >>>> > file name and date). >>>> > >>>> > But maybe you're on the right track: It does seem like QS is >>>> trying >>>> > to load the file; I looked more carefully and when QS hangs doing >>>> > this, its memory usage (as shown in activity monitor) skyrockets. >>>> I >>>> > just killed it when it was using around 4.6 GB and still going >>>> up. >>>> > So I suppose it's trying to load the file to memory, and that's >>>> what >>>> > causes the hang. >>>> > >>>> > I just did more testing, and it seems I was wrong: this also >>>> happens >>>> > with 10 gb files, as long as they have no extension. >>>> > I also tested a 1.6 GB file. It only hangs QS for a while (a >>>> while >>>> > during which its memory usage races up to 1.6 GB...) and then >>>> > continues normally (memory usage goes down after I continue). >>>> > >>>> > What's going on here! >>>> > >>>> > PS. (to Patrick) I just restarted QS and suddenly, a gazillon >>>> > messages showed up in the console (so many in such a short period >>>> > that it exceeded the 500 messages per second limit). I am sending >>>> > the logs attached, but I'm not sure this is related to my other >>>> problem. >>>> > >>>> > >>>> > On Thursday, July 26, 2012 7:17:10 PM UTC-3, Daniel wrote: >>>> > >>>> > Do you have QLStephen or another QuickLook plugin that might >>>> try >>>> > to create a preview for no-extension files? If you can >>>> QuickLook >>>> > the file in Finder, this isn't the issue. >>>> > >>>> > If this is the issue, my guess is that the TrueCrypt volume >>>> > header looks like valid ASCII for the first however many >>>> bytes >>>> > `file` looks at to guess the encoding, while your example >>>> 10GB >>>> > file doesn't�so in the one case it's trying to interpret it >>>> all >>>> > as ASCII text, while in the other case it just gives up. >>>> > >>>> > This is just the first thing that came to mind, it could >>>> easily >>>> > be something completely unrelated. >>>> > >>>> > On Thursday, July 26, 2012 10:48:58 AM UTC-4, koro wrote: >>>> > >>>> > I have a very large file (20 GB) with no extension, which >>>> is >>>> > a Truecrypt container. When it shows up in the first pane >>>> of >>>> > the latest quicksilver version, I automatically get a >>>> beach >>>> > ball and QS hangs; I have to manually kill it and >>>> restart. >>>> > >>>> > I can't find an explanation for this. I have tested and: >>>> > 1) the problem stops if i change the file name to >>>> something >>>> > with an extension (like file.ext) >>>> > 2) i tested a 10 GB file (which is the second largest >>>> file I >>>> > could find) after removing its extension, and I don't get >>>> > the same problem. >>>> > >>>> > So there's something special about this file having no >>>> > extension AND there's something special about this >>>> > particular file or its size of 20GB (that does not happen >>>> > with 10GB) >>>> > >>>> > Any ideas? >>>> > >>>> > -- You received this message because you are subscribed to the >>>> > Google Groups Quicksilver group. To post to this group, send >>>> email >>>> > to >>>> > blacktree-quicksilver@**googlegroups.com<[email protected]> >>>> > >>>> > >>>> > <mailto:blacktree-quicksilver@**googlegroups.com<[email protected]>>. >>>> > >>>> To unsubscribe from >>>> > this group, send email to >>>> > >>>> > blacktree-quicksilver+**[email protected]<blacktree-quicksilver%[email protected]> >>>> > >>>> > >>>> > <mailto:blacktree-quicksilver%**[email protected]<blacktree-quicksilver%[email protected]> >>>> **>. For >>>> > more options, visit this group at >>>> > >>>> > https://groups.google.com/d/**forum/blacktree-quicksilver?**hl=en<https://groups.google.com/d/forum/blacktree-quicksilver?hl=en> >>>> > >>>> > >>>> > >>>> > -- You received this message because you are subscribed to the Google >>>> > Groups Quicksilver group. To post to this group, send email to >>>> > blacktree-quicksilver@**googlegroups.com<[email protected]>. >>>> > >>>> To unsubscribe from this group, >>>> > send email to >>>> > blacktree-quicksilver+**[email protected]<blacktree-quicksilver%[email protected]>. >>>> > >>>> For >>>> > more options, visit this group at >>>> > https://groups.google.com/d/**forum/blacktree-quicksilver?**hl=en<https://groups.google.com/d/forum/blacktree-quicksilver?hl=en> >>>> > >>>> >>>> -- You received this message because you are subscribed to the Google >> Groups Quicksilver group. To post to this group, send email to >> [email protected]. To unsubscribe from this group, >> send email to [email protected]. For >> more options, visit this group at >> https://groups.google.com/d/forum/blacktree-quicksilver?hl=en >> > >
-- You received this message because you are subscribed to the Google Groups Quicksilver group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at https://groups.google.com/d/forum/blacktree-quicksilver?hl=en
