View Single Post
Old 08-01-2012, 12:58 AM   #4
seabream
Enthusiast
seabream can extract oil from cheeseseabream can extract oil from cheeseseabream can extract oil from cheeseseabream can extract oil from cheeseseabream can extract oil from cheeseseabream can extract oil from cheeseseabream can extract oil from cheeseseabream can extract oil from cheese
 
Posts: 48
Karma: 1056
Join Date: Jul 2012
Location: Central Canada
Device: Sony PRS-T1, RIM Playbook & Z10, Samsung Note, MacOSX
Quote:
I guess something slipped in
Or perhaps not.
Quote:
Originally Posted by JimmXinu View Post
@seabream - I've combed through my code and FFDL does save explicit references to all it's menu updates--twice, in fact.
After testing a bunch of different beta versions of FFDL (thanks for doing so much work JimmXinu), some more successful than others, for unrelated reasons I installed Java update for Mac OSX 10.7 Update 1 (http://support.apple.com/kb/HT5045) and 2012-4 (http://support.apple.com/kb/HT5319), (and DroboDashboard 2.2.1, updated from 2.1.2, but that really shouldn't have anything to do with it) and restarted the computer as required, and now the same stock FFDL 1.6.0 that was crashing before is actually stable for the moment. I'll try more stuff with it and still be using it of course, so fingers crossed to see whether it lasts. I'd think that the Java version shouldn't have an effect, but JimmXinu pointed out that it apparently has before (http://oldbugs.calibre-ebook.com/ticket/1859), so who knows.

So if anyone else is having this issue, check your Java maybe? I'm not completely sure which version I was at before. I just upgraded to Lion from Snow Leopard a few weeks ago, and was current with updates at the time, so it should have been either Java Update for Mac OS X 10.6 Update 8 or 9, but I don't know for sure what gets replaced when updating the OS. Funny enough, Java update 1 didn't show up on its own in Software Update, despite being released in Nov 2011. I saw it because I was prompted to install a version of Java greater than 1.5 by the DroboDashboard installer in order to use the iSCSI connection with the Drobo, which would seem to indicate that my Java version was older, non-existent, or not active. If anyone has any insight as to why there might be an interaction, both JimmXinu and I are puzzled and would be interested to know.

Last edited by seabream; 08-01-2012 at 01:24 AM. Reason: Added info about previous Java and DroboDashboard versions.
seabream is offline   Reply With Quote