View Single Post
Old 09-04-2016, 02:44 AM   #6
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
As Kovid said before, calibre contains no kernel code and is physically incapable of causing that crash.

The problem is going to be somewhere in the interaction between the kernel driver for that adapter, and the various pieces of software which calibre makes use of -- none of which are under calibre's control and several of which are part of OSX itself.

...

Apparently, calibre can activate this bug by running certain codepaths which aren't usually accessed on your computer.
But the most that anyone here can do is help you figure out where that interaction is taking place, so you can report a bug to whichever project is responsible for the real cause of that crash.

Hopefully, someone has an idea...
eschwartz is offline   Reply With Quote