Segmentation fault

weedfreak · 09-19-2009, 04:46 AM

I was getting two or three crashes an hour with segmentation fault using 6.12 on Xubuntu jaunty 64 bit, but waited patiently for the next upgrade as I had read posts that it was being dealt with.

On restarting today I was advised the upgrade was available so I up graded to 6.13, unfortunately I can no longer start Calibre, I get a segmentation fault every time, with 6.12 it never took more than 6 attempts to start.

I tried calibre debug and the app loaded, I closed it and tried just calibre and this time it worked, so it could of been some spurious data from the last 6.12 crash ?? Anyway I shall carry on sorting out the metatags from my library and see how stable this version is.

kovidgoyal · 09-19-2009, 10:32 AM

I'm going to need an strace to debug crashes. calibre is pretty stable on my 64-bit system, so it's likely an interaction with some dependency. strace will help me find that.

The bug fixes with respect to stability in 0.6.12 were platform neutral ones (an reference cycle that the Python garbage collector couldn't handle leading to a memory leak when queueing books for conversion)

strace -f calibre

weedfreak · 09-19-2009, 11:02 AM

In fact since the initial start-up problems 6.13 has been running pretty stable here as well. There was one crash while editing meta data but that was before you asked for an strace so I have no input.
I'll post back with an strace if I get further problems, until then no news is good news.

weedfreak · 09-20-2009, 05:27 AM

Only one crash so far -

Code:

Traceback (most recent call last):
  File "/home/kovid/work/calibre/src/calibre/gui2/dialogs/metadata_single.py", line 66, in run
  File "/home/kovid/work/calibre/src/calibre/ebooks/metadata/library_thing.py", line 61, in cover_from_isbn
ISBNNotFound: ISBN: 9789999979511 not found.

Traceback (most recent call last):
  File "/home/kovid/work/calibre/src/calibre/library/database2.py", line 744, in notify
  File "/home/kovid/work/calibre/src/calibre/gui2/tag_view.py", line 104, in database_changed
  File "/home/kovid/work/calibre/src/calibre/gui2/tag_view.py", line 108, in refresh
  File "/home/kovid/work/calibre/src/calibre/library/database2.py", line 1001, in get_categories
  File "/home/kovid/work/calibre/src/calibre/library/database2.py", line 994, in get
SystemError: Objects/dictobject.c:681: bad argument to internal function
Segmentation fault

Hope this helps!

kovidgoyal · 09-20-2009, 11:35 AM

Do you remember what you were doing when this happened?

weedfreak · 09-20-2009, 03:08 PM

I was editing metatags in general and I think I was specifically connecting to isbndb to check details or d/l the book cover.

kovidgoyal · 09-20-2009, 03:12 PM

This was with the edit metadata dialog, or just in the main GUI?

weedfreak · 09-21-2009, 03:14 AM

Metadata dialog, edit metadata individually

kovidgoyal · 09-21-2009, 09:48 AM

OK, I have an idea about what may be causing this, I'll look into it.

weedfreak · 10-01-2009, 01:41 PM

Firstly things seem a lot more stable with 6.14.
I did get a database out of range error when adding a new book by drag 'n' drop, checking db integrity produced no errors but shorly afterwards I got this error and ctd.

Code:

ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to objects owned by a different thread. Current thread 5a8fb30. Receiver '' (of type 'QWidget') was created in thread 39120d0", file kernel/qcoreapplication.cpp, line 305

The book added when the db range error occurred seems to be intact and I was searching for another book at the time of the fatal crash.

kovidgoyal · 10-01-2009, 02:47 PM

The range errors will be fixed in the enxt release

09-19-2009, 04:46 AM	#1
weedfreak Addict Posts: 302 Karma: 185297 Join Date: Sep 2009 Location: Ankh Morpork Device: calibre	Segmentation fault I was getting two or three crashes an hour with segmentation fault using 6.12 on Xubuntu jaunty 64 bit, but waited patiently for the next upgrade as I had read posts that it was being dealt with. On restarting today I was advised the upgrade was available so I up graded to 6.13, unfortunately I can no longer start Calibre, I get a segmentation fault every time, with 6.12 it never took more than 6 attempts to start. I tried calibre debug and the app loaded, I closed it and tried just calibre and this time it worked, so it could of been some spurious data from the last 6.12 crash ?? Anyway I shall carry on sorting out the metatags from my library and see how stable this version is.

10-01-2009, 01:41 PM	#10
weedfreak Addict Posts: 302 Karma: 185297 Join Date: Sep 2009 Location: Ankh Morpork Device: calibre	Firstly things seem a lot more stable with 6.14. I did get a database out of range error when adding a new book by drag 'n' drop, checking db integrity produced no errors but shorly afterwards I got this error and ctd. Code: ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to objects owned by a different thread. Current thread 5a8fb30. Receiver '' (of type 'QWidget') was created in thread 39120d0", file kernel/qcoreapplication.cpp, line 305 The book added when the db range error occurred seems to be intact and I was searching for another book at the time of the fatal crash.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Segmentation Fault when adding books to Calibre 0.7.13	TuxGirl	Calibre	10	08-12-2010 11:47 PM
Segmentation fault trying to run Calibre on CentOS 5.5	midders	Calibre	1	07-26-2010 11:32 AM
Unutterably Silly Whose fault is it?	Logseman	Lounge	59	03-25-2010 12:10 AM
Segmentation Fault after Qt upgrade	reader42	Calibre	8	03-21-2010 06:58 PM
Its Oprahs Fault!	desertgrandma	Amazon Kindle	5	11-01-2008 11:16 PM

09-19-2009, 10:32 AM	#2
kovidgoyal creator of calibre Posts: 45,156 Karma: 27110894 Join Date: Oct 2006 Location: Mumbai, India Device: Various	I'm going to need an strace to debug crashes. calibre is pretty stable on my 64-bit system, so it's likely an interaction with some dependency. strace will help me find that. The bug fixes with respect to stability in 0.6.12 were platform neutral ones (an reference cycle that the Python garbage collector couldn't handle leading to a memory leak when queueing books for conversion) strace -f calibre

09-19-2009, 11:02 AM	#3
weedfreak Addict Posts: 302 Karma: 185297 Join Date: Sep 2009 Location: Ankh Morpork Device: calibre	In fact since the initial start-up problems 6.13 has been running pretty stable here as well. There was one crash while editing meta data but that was before you asked for an strace so I have no input. I'll post back with an strace if I get further problems, until then no news is good news.

09-20-2009, 11:35 AM	#5
kovidgoyal creator of calibre Posts: 45,156 Karma: 27110894 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Do you remember what you were doing when this happened?

09-20-2009, 03:08 PM	#6
weedfreak Addict Posts: 302 Karma: 185297 Join Date: Sep 2009 Location: Ankh Morpork Device: calibre	I was editing metatags in general and I think I was specifically connecting to isbndb to check details or d/l the book cover.

09-20-2009, 03:12 PM	#7
kovidgoyal creator of calibre Posts: 45,156 Karma: 27110894 Join Date: Oct 2006 Location: Mumbai, India Device: Various	This was with the edit metadata dialog, or just in the main GUI?

09-21-2009, 03:14 AM	#8
weedfreak Addict Posts: 302 Karma: 185297 Join Date: Sep 2009 Location: Ankh Morpork Device: calibre	Metadata dialog, edit metadata individually

09-21-2009, 09:48 AM	#9
kovidgoyal creator of calibre Posts: 45,156 Karma: 27110894 Join Date: Oct 2006 Location: Mumbai, India Device: Various	OK, I have an idea about what may be causing this, I'll look into it.

10-01-2009, 02:47 PM	#11
kovidgoyal creator of calibre Posts: 45,156 Karma: 27110894 Join Date: Oct 2006 Location: Mumbai, India Device: Various	The range errors will be fixed in the enxt release

Advert

Advert