CC Problem

[scarlettruin]

I'm sorry if this is completely useless - i don't know tonnes about computers! :S something is up with my CC. It is incredibly slow and crashes constantly, especially if I try to use tags in the grouping. I've re-started my device twice and I've scanned the device for viruses, etc. Can anyone help please?

Thank you!!

[chaley]

Originally Posted by scarlettruin

I'm sorry if this is completely useless - i don't know tonnes about computers! :S something is up with my CC. It is incredibly slow and crashes constantly, especially if I try to use tags in the grouping. I've re-started my device twice and I've scanned the device for viruses, etc. Can anyone help please?

Thank you!!

Please send me a CC debug log by in CC going to Settings, scrolling all the way down, and choosing "Send a debug log to multipie". There will be two destination email addresses shown. Clear the one to "multipie.co.uk" (my son). There isn't any reason to take his time if I am looking at it.

[scarlettruin]

Originally Posted by chaley

Please send me a CC debug log by in CC going to Settings, scrolling all the way down, and choosing "Send a debug log to multipie". There will be two destination email addresses shown. Clear the one to "multipie.co.uk" (my son). There isn't any reason to take his time if I am looking at it.

I've sent it to you - please tell me if there's anything else you need!

Thanks!

S

[chaley]

I have looked at the debug log and I am confused. There are no crash traces in the log so I can't say for sure what is happening. I do see that you tapped on "Tags" in the grouping drawer and then CC restarted, so that must be a crash. I assume you are seeing some dialog saying "Unfortunately Calibre Companion has stopped" (or something like that) where you are offered a choice to send the crash report. Next time, please say yes, send the report.

The second thing I see is that the initial grouping by tags is taking around 45 seconds. This is far longer than it should be. My guess is that your device doesn't have a lot memory, that you have a lot of books (the log says 4112), and you have a lot of tags. My guess is corroborated by the apparent crashes (sometimes) during this process. It is interesting to note that clicking on an individual tag responds in less than a 10th of a second. This speed corroborates that some limit is being reached with the number of tags and the number of books.

There isn't much I can do about this second problem in the current release. However, someone has requested an option to remove the counts from the grouping drawer, which I intend to implement in the next cycle. Removing these counts might reduce the database load enough to avoid the long time and the crashes.

In the meantime, I suspect that if you reduce the number of books on the device then the performance problem and crashes will go away. I don't know what number of books is "good".

[scarlettruin]

Originally Posted by chaley

I have looked at the debug log and I am confused. There are no crash traces in the log so I can't say for sure what is happening. I do see that you tapped on "Tags" in the grouping drawer and then CC restarted, so that must be a crash. I assume you are seeing some dialog saying "Unfortunately Calibre Companion has stopped" (or something like that) where you are offered a choice to send the crash report. Next time, please say yes, send the report.

The second thing I see is that the initial grouping by tags is taking around 45 seconds. This is far longer than it should be. My guess is that your device doesn't have a lot memory, that you have a lot of books (the log says 4112), and you have a lot of tags. My guess is corroborated by the apparent crashes (sometimes) during this process. It is interesting to note that clicking on an individual tag responds in less than a 10th of a second. This speed corroborates that some limit is being reached with the number of tags and the number of books.

There isn't much I can do about this second problem in the current release. However, someone has requested an option to remove the counts from the grouping drawer, which I intend to implement in the next cycle. Removing these counts might reduce the database load enough to avoid the long time and the crashes.

In the meantime, I suspect that if you reduce the number of books on the device then the performance problem and crashes will go away. I don't know what number of books is "good".

Okay, thank you. It does say 'unfortunately calibre companion has stopped' and i've sent the report twice. I'll take your advice and reduce the number of books and tags on my device.

Thank you again

S

[chaley]

Originally Posted by scarlettruin

Okay, thank you. It does say 'unfortunately calibre companion has stopped' and i've sent the report twice. I'll take your advice and reduce the number of books and tags on my device.

Thank you again

S

The last report we received was on Jun 29, from a device type "fiber-bs1078" running Android 4.4. Your device is a "SM-T210" and appears to be running Android 4.2. I wonder what happened to your reports? Perhaps they are in a queue somewhere and we will eventually get them. I hope so.

Unless you want to reduce your tag count anyway, start with reducing the number of books. That is a relatively easy way to check if the problem goes away.

[scarlettruin]

Originally Posted by chaley

The last report we received was on Jun 29, from a device type "fiber-bs1078" running Android 4.4. Your device is a "SM-T210" and appears to be running Android 4.2. I wonder what happened to your reports? Perhaps they are in a queue somewhere and we will eventually get them. I hope so.

Unless you want to reduce your tag count anyway, start with reducing the number of books. That is a relatively easy way to check if the problem goes away.

That's odd...anyway, I'll take your advice.
Thanks for the help!

S