Error on import

[kovidgoyal]

Uninstall calibre, install the 32 bit version.

As for logs, there can be no calibre logs since the calibre worker process is being killed by something external to it. I know of no way to find out what external process kills another process.

[MikeyTsi]

What's the difference, some performance loss?

[BetterRed]

Originally Posted by MikeyTsi

What's the difference, some performance loss?

Main difference is on large conversions which need lots of memory - they will fail. Day to day stuff doesn't make any noticeable difference. There are plenty of users who use the 32bit version by way of using the Portable version and they never run into the limits, I think books with very large numbers of internal links are problematic.

It doubt it is of any consolation, but you're not the first person to run into this situation, when the 64 bit has 'weird' errors and the 32bit works.

Just recently, Kovid told us how to create a 64bit Portable ==>> Calibre portable 64bit. It's very simple, and you already have the wherewithal to do it -- it won't solve the problem, but it would confirm that it's a bittedness issue.

Have you tried Safe Mode, and running with minimal number of processes, I'm thinking of startup tasks, windows shell extensions, 3rd party codecs, unusual devices etc.

BR

[theducks]

Originally Posted by MikeyTsi

What's the difference, some performance loss?

For you: A performance gain. From Not working to Working

Why are you arguing? You asked for help.

Every system is different. There is no Perfect answer. (and remember: 'It is Windows" )
Do or Don't do

We will attempt to warn of hazards (posting malicious tips will get a person banned. The Mods will pounce).
A Backup of the Library FOLDER is the first thing that should be done when things go sideways.

[MikeyTsi]

Originally Posted by BetterRed

Main difference is on large conversions which need lots of memory - they will fail. Day to day stuff doesn't make any noticeable difference. There are plenty of users who use the 32bit version by way of using the Portable version and they never run into the limits, I think books with very large numbers of internal links are problematic.

It doubt it is of any consolation, but you're not the first person to run into this situation, when the 64 bit has 'weird' errors and the 32bit works.

Just recently, Kovid told us how to create a 64bit Portable ==>> Calibre portable 64bit. It's very simple, and you already have the wherewithal to do it -- it won't solve the problem, but it would confirm that it's a bittedness issue.

Have you tried Safe Mode, and running with minimal number of processes, I'm thinking of startup tasks, windows shell extensions, 3rd party codecs, unusual devices etc.

BR

It's a Surface Pro 3 with an external drive attached, there isn't really anything special going on.
"Resident" apps are AVG, Steam, GOG Galaxy, OneDrive, OneNote, nothing really special. I typically have Trillian, Firefox, Outlook actually running.

The only thing I can reasonably think of causing a problem is that I'm on the tech preview for Windows; it's possible that the current release I'm on has a bug. If that's the case I'd like to report it but I'd probably need to be able to collect more data for investigation.

I was asking about performance since 32-bit applications handle addressing differently, plus there are limitations on how much memory they can access, and is definitely a factor in 32-bit vs 64-bit operating systems.

[MikeyTsi]

Two more questions.

1. Can you run parallel installs of both the 32 and 64-bit applications?
2. Is the Calibre config (on mine in AppData\Roaming\Calibre) portable between the two versions? If so that would be rad since I won't have to rebuild my config.

[theducks]

Originally Posted by MikeyTsi

Two more questions.

1. Can you run parallel installs of both the 32 and 64-bit applications?
2. Is the Calibre config (on mine in AppData\Roaming\Calibre) portable between the two versions? If so that would be rad since I won't have to rebuild my config.

The Config is Shared between 32 and 64 bit.

Only run one at a time

[MikeyTsi]

Well hey, that makes things easier. I'll just test periodically to see if x64 starts working.

[BetterRed]

Originally Posted by MikeyTsi

The only thing I can reasonably think of causing a problem is that I'm on the tech preview for Windows; it's possible that the current release I'm on has a bug.

More than probable - that's why MS gets outsiders to do their testing for them - to find the bugs.

If you ran the Insider releases in a VM , you would be better able to to test the MS code for them. Hey MS - 'this' works on this production version of Windows, but it crashes on the latest preview version - how come?

BR

[MikeyTsi]

I submitted a bug report, which included repro on 64-bit, then demonstrating it working on 32-bit while running monitoring. We'll see if anything comes of it.

Until then, I can work around the issue with the 32-bit version.