Quote:
Originally Posted by cybmole
it might be easier to have a special debug testing version of calibre which put up lots more "progress messages" to screen during the initial load, or wrote same to a log file with timestamps. that should highlight where in the start sequence the freeze is occurring
|
I think the problem is some sort of 'interaction' between calibre and something else.
If you agree with that then I have to ask... how would sprinkling printfs in the code identify the 'something else'.
Besides which, have we not established its probably something related to device scanning. That would suggest a driver or similar issue - basically the sort of thing in the
calibre freezes/crashes occasionally? scenario.
But - why not do both, tracing in the code and some system comparisons.
I'm happy to swap my system specs with HarryT, DrChiper and JeanPaulo via PM. I'll leave the ball in their courts.
BR