CC (multipie version) is crashing Calibre

theducks · 10-28-2022, 07:46 AM

My old reliable CC (multipie version) is crashing Calibre SILENTLY.
No debug log, even when Calibre started in that mode.

Wireless device connections connects (on device column appears ) and then Calibre closes (poof

) after a few seconds.
Calibre 6.7.1 monitor beta
Been a while since I tried using CC, so I don't know how long I have had issues.

I did try and delete the device_drivers_SMART_DEVICE_APP.py files, no joy.

AFAIK CC is working otherwise.

Could it be a corrupt metadata.calibre on the device?
But the bigger issue IMHO, is the silent fail for whatever reason.

kovidgoyal · 10-28-2022, 09:58 AM

run calibre in debug mode and post the log after the crash

theducks · 10-28-2022, 10:49 AM

Quote:

Originally Posted by kovidgoyal

run calibre in debug mode and post the log after the crash

I did run it in debug. No log was made (or the message never showed and I can't find).
Found the log after the abend
I see nothing about the WDC

kovidgoyal · 10-28-2022, 11:08 AM

Hmm there doesnt even seem to be any output indicating the wiresless device is connecting. Try running calibre as

calibre-debug -g

in a command prompt maybe that will show more.

Also you are running the beta maybe switch back to the release and see if it makes a difference.

theducks · 10-28-2022, 06:49 PM

The released version 6.7.1 runs fine

kovidgoyal · 10-28-2022, 11:19 PM

Hmm that's ominous. I dont actually have a way to test the wireless driver unfortunately to see what might be happening.

theducks · 10-28-2022, 11:25 PM

Quote:

Originally Posted by kovidgoyal

Hmm that's ominous. I dont actually have a way to test the wireless driver unfortunately to see what might be happening.

Does anybody other than CC use that? Since CC is mostly dead...
It has been months since I used it.

Wasn't the beta just a dual monitor thing? Why would it affect the WDC driver?

kovidgoyal · 10-28-2022, 11:35 PM

I think there are one or two other apps that use that driver. The beta was basically all changes up to the monitor stuff, so there are some other changes, for example to the search bar as well. I cant think of any changes that could affect the driver which is why I am at a loss.

theducks · 10-29-2022, 12:04 AM

Quote:

Originally Posted by kovidgoyal

I think there are one or two other apps that use that driver. The beta was basically all changes up to the monitor stuff, so there are some other changes, for example to the search bar as well. I cant think of any changes that could affect the driver which is why I am at a loss.

When I get a chance, I will try the beta again with the command debug.
(It was a solid fail, at least 6 times)

chaley · 10-29-2022, 09:04 AM

Well, this was fun.

The problem was introduced in commit 8b270da, 17 Oct, when the ability to call stored python templates added. The python caller class is instantiated by the formatter. Unfortunately the caller class cached a copy of the formatter instance, which was never nulled.

When metadata.book.deepcopy() makes a copy of a book Metadata object it makes a copy of the Metadata's formatter instance. Because of the above commit that instance contains a pointer to itself, so we have infinite recursion. Bang.

Fix submitted.

kovidgoyal · 10-29-2022, 10:00 AM

@charles: thanks, this would have been very difficult for me to debug.

theducks · 10-29-2022, 12:00 PM

to both of you. I am glad I spotted it early and gave you enough to track it down.

I've never had a Calibre fail so spectacularly before.

enuddleyarbl · 10-29-2022, 12:06 PM

I keep thinking I should try to get into coding again so I could try helping with things like this. But, things are so different since I used to run my deck of punched cards through the card reader, wait a couple of days for the printout, and find I messed up my JCL. Not only do I not understand a word of what chaley said as a solution, I don't understand a word of what theducks said was the problem.

Anyway, it's amazing what people can (and do) do here.

ownedbycats · 10-29-2022, 06:39 PM

Quote:

Originally Posted by enuddleyarbl

I keep thinking I should try to get into coding again so I could try helping with things like this. But, things are so different since I used to run my deck of punched cards through the card reader, wait a couple of days for the printout, and find I messed up my JCL. Not only do I not understand a word of what chaley said as a solution, I don't understand a word of what theducks said was the problem.

Anyway, it's amazing what people can (and do) do here.

One way to help is when you find a bug, figure out how to replicate it before submitting the report. "This feature is broken

" is probably less useful than "When I do the following steps, Calibre behaves in this way." Here's how I usually do bug reports.

DNSB · 10-30-2022, 02:01 AM

Quote:

Originally Posted by ownedbycats

One way to help is when you find a bug, figure out how to replicate it before submitting the report. "This feature is broken

" is probably less useful.[/url]

You want bug reports to contain more that "It doesn't work"? Or my all time favorite, "I didn't do anything and it stopped working."

10-28-2022, 07:46 AM	#1
theducks Well trained by Cats Posts: 31,057 Karma: 60358908 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	CC (multipie version) is crashing Calibre My old reliable CC (multipie version) is crashing Calibre SILENTLY. No debug log, even when Calibre started in that mode. Wireless device connections connects (on device column appears ) and then Calibre closes (poof ) after a few seconds. Calibre 6.7.1 monitor beta Been a while since I tried using CC, so I don't know how long I have had issues. I did try and delete the device_drivers_SMART_DEVICE_APP.py files, no joy. AFAIK CC is working otherwise. Could it be a corrupt metadata.calibre on the device? But the bigger issue IMHO, is the silent fail for whatever reason.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kobo database version unsupported + Error when trying to update Calibre to version 6.	Maria Loranger	Devices	35	09-12-2023 09:40 AM
Calibre 5.0 Wireless Device Connection Crashing Calibre Companion	datostar	Calibre	3	10-05-2020 11:50 PM
How to migrate from Calibre's portable version to Calibre's PortableApps version	gohhwaian	Calibre	2	07-02-2018 01:30 PM
sigil 7.4 and maverick crashing crashing crashing	Carrigboy	Sigil	103	09-04-2014 11:47 AM
Version 0.8.26 crashing my pc when converting	Acousticvillage	Calibre	0	11-17-2011 05:18 PM

10-28-2022, 09:58 AM	#2
kovidgoyal creator of calibre Posts: 45,351 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	run calibre in debug mode and post the log after the crash

10-28-2022, 11:08 AM	#4
kovidgoyal creator of calibre Posts: 45,351 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Hmm there doesnt even seem to be any output indicating the wiresless device is connecting. Try running calibre as calibre-debug -g in a command prompt maybe that will show more. Also you are running the beta maybe switch back to the release and see if it makes a difference.

10-28-2022, 06:49 PM	#5
theducks Well trained by Cats Posts: 31,057 Karma: 60358908 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	The released version 6.7.1 runs fine

10-28-2022, 11:19 PM	#6
kovidgoyal creator of calibre Posts: 45,351 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Hmm that's ominous. I dont actually have a way to test the wireless driver unfortunately to see what might be happening.

10-28-2022, 11:35 PM	#8
kovidgoyal creator of calibre Posts: 45,351 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	I think there are one or two other apps that use that driver. The beta was basically all changes up to the monitor stuff, so there are some other changes, for example to the search bar as well. I cant think of any changes that could affect the driver which is why I am at a loss.

10-29-2022, 09:04 AM	#10
chaley Grand Sorcerer Posts: 12,447 Karma: 8012886 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	Well, this was fun. The problem was introduced in commit 8b270da, 17 Oct, when the ability to call stored python templates added. The python caller class is instantiated by the formatter. Unfortunately the caller class cached a copy of the formatter instance, which was never nulled. When metadata.book.deepcopy() makes a copy of a book Metadata object it makes a copy of the Metadata's formatter instance. Because of the above commit that instance contains a pointer to itself, so we have infinite recursion. Bang. Fix submitted.

10-29-2022, 10:00 AM	#11
kovidgoyal creator of calibre Posts: 45,351 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	@charles: thanks, this would have been very difficult for me to debug.

10-29-2022, 12:00 PM	#12
theducks Well trained by Cats Posts: 31,057 Karma: 60358908 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	to both of you. I am glad I spotted it early and gave you enough to track it down. I've never had a Calibre fail so spectacularly before.

10-29-2022, 12:06 PM	#13
enuddleyarbl Guru Posts: 776 Karma: 1538394 Join Date: Sep 2013 Device: Kobo Forma	I keep thinking I should try to get into coding again so I could try helping with things like this. But, things are so different since I used to run my deck of punched cards through the card reader, wait a couple of days for the printout, and find I messed up my JCL. Not only do I not understand a word of what chaley said as a solution, I don't understand a word of what theducks said was the problem. Anyway, it's amazing what people can (and do) do here.