Startup crash

Phyrefly · 06-17-2011, 11:03 AM

I have just installed Calibre, and attempted to import 1000s of books. It took a while (understandably) but when it had finished, there were only 7 books in calibre. It seems that while it ran through many subfolders, it only imported the ones in the root. I have tried drag&drop importing some of these folders one at a time, and they seem to work, to a point. The metadata is messed up, but I can fix that... let's just get the books in.

So I've done this with a few folders, then try to open a book, and calibre crashed (just closed, with a Win7 "the application has stopped working" message). Now when I run it, I get the same thing again - immediately, before the GUI even presents itself (I do get the splash screen).

So query 1 is - what's gone wrong, and how can I fix it without access to the GUI?

and query 2 is - if I can get it working again - how do I import my books without having to drag&drop from each folder? Is there a way to import from a whole dir structure?

Thanks,
Rich

kovidgoyal · 06-17-2011, 11:21 AM

1) http://manual.calibre-ebook.com/faq....ing-on-windows

2) click the arrow next to the add books button

Phyrefly · 06-17-2011, 12:27 PM

Thanks for the swift reply...
1) - none of those things helped, but debug-mode showed something, details below.
2) - thanks, that's better!

So, my computer has something slowly killing it, at the moment it's super-sensitive to memory leaks. Anything that is leaking kills it eventually. That's what happened here, a reboot means I can run calibre again. But it didn't show the error message that I get from any other app before it died, it just dissapeared on me. (Debug-mode showed the error). This may not be the best result from an error-handling point of view... The memory leak probably isn't in Calibre by the way (or at least, isn't necessarily in it) - killing Calibre was just a symptom.

06-17-2011, 11:03 AM	#1
Phyrefly Junior Member Posts: 5 Karma: 10 Join Date: Jun 2011 Device: iRiver Cover Story	Startup crash I have just installed Calibre, and attempted to import 1000s of books. It took a while (understandably) but when it had finished, there were only 7 books in calibre. It seems that while it ran through many subfolders, it only imported the ones in the root. I have tried drag&drop importing some of these folders one at a time, and they seem to work, to a point. The metadata is messed up, but I can fix that... let's just get the books in. So I've done this with a few folders, then try to open a book, and calibre crashed (just closed, with a Win7 "the application has stopped working" message). Now when I run it, I get the same thing again - immediately, before the GUI even presents itself (I do get the splash screen). So query 1 is - what's gone wrong, and how can I fix it without access to the GUI? and query 2 is - if I can get it working again - how do I import my books without having to drag&drop from each folder? Is there a way to import from a whole dir structure? Thanks, Rich

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
0.7.56 Crash on startup: "'QWidget' Object has no attribute 'fillier'"	MrAndreBB	Calibre	0	04-17-2011 01:44 PM
Please help! Stuck at startup	Orochi	Kobo Reader	5	12-24-2010 08:57 AM
Frozen at startup	Mememememe	Kobo Reader	1	05-27-2010 01:04 PM
UnicodeDecodeError in startup.py	yet	Calibre	0	02-04-2010 05:57 AM
iLiad Autorun on startup	tribble	iRex Developer's Corner	1	11-23-2006 02:01 PM

06-17-2011, 11:21 AM	#2
kovidgoyal creator of calibre Posts: 45,209 Karma: 27110894 Join Date: Oct 2006 Location: Mumbai, India Device: Various	1) http://manual.calibre-ebook.com/faq....ing-on-windows 2) click the arrow next to the add books button

06-17-2011, 12:27 PM	#3
Phyrefly Junior Member Posts: 5 Karma: 10 Join Date: Jun 2011 Device: iRiver Cover Story	Thanks for the swift reply... 1) - none of those things helped, but debug-mode showed something, details below. 2) - thanks, that's better! So, my computer has something slowly killing it, at the moment it's super-sensitive to memory leaks. Anything that is leaking kills it eventually. That's what happened here, a reboot means I can run calibre again. But it didn't show the error message that I get from any other app before it died, it just dissapeared on me. (Debug-mode showed the error). This may not be the best result from an error-handling point of view... The memory leak probably isn't in Calibre by the way (or at least, isn't necessarily in it) - killing Calibre was just a symptom.

Advert