Bug: File -> Quit: editor crashes

Katsunami · 02-14-2014, 02:31 PM

Relevant specifications:

Windows 7 64-bit
Calibre 1.24 64-bit
Removed installation and re-installed (did not remove settings)

Steps to take:

1. Open any EPUB book in Editor (I've tested 4. 3 originals, 1 converted from AZW3.)
2. Click File->Quit.
3. The Editor does nothing. No feedback.
4. Click anything: Crash. Windows kills the program.

Additional information: the editor quits as normal when using:
- X close button
- Right-click titlebar -> Close
- System menu -> Close
- ALT-F4

The editor functions seem to work as normal, at least in the short while I've been able to use them in version 1.24.

DrChiper · 02-14-2014, 03:15 PM

Confirmed. Only, Edit Book does not crash but rather does not respond anymore. I have to manually close the program from pop-up window.
BTW: I'm using calibre 1.24 32bit

mrmikel · 02-14-2014, 03:15 PM

Verified with same setup here.

Katsunami · 02-14-2014, 03:24 PM

Quote:

Originally Posted by DrChiper

Confirmed. Only, Edit Book does not crash but rather does not respond anymore. I have to manually close the program from pop-up window.
BTW: I'm using calibre 1.24 32bit

When clicking File->Quit, the Editor stops responding. Then, when clicking anything else (in the Editor), Windows pops up the "This program needs to be closed" dialog.

AFAIK, that's a crash

mrmikel · 02-14-2014, 03:28 PM

Did you ever see Crocodile Dundee? "Now That's a Knife" How about a blue screen of death? (grin)

Katsunami · 02-14-2014, 03:37 PM

Quote:

Originally Posted by mrmikel

Did you ever see Crocodile Dundee? "Now That's a Knife" How about a blue screen of death? (grin)

I have seen only a few BSOD's in the last 15 years (I'm on Windows NT since 1996, and never used 95, 98, or ME), and they were all caused by a crappy hardware driver. BSOD's are not regular occurences here. Neither are re-installs: this installation now runs for almost 6 years, and actually is an in-place upgrade from a previous Windows Vista install.

gbm · 02-14-2014, 04:21 PM

Quote:

Originally Posted by Katsunami

Relevant specifications:

Windows 7 64-bit
Calibre 1.24 64-bit
Removed installation and re-installed (did not remove settings)

Steps to take:

1. Open any EPUB book in Editor (I've tested 4. 3 originals, 1 converted from AZW3.)
2. Click File->Quit.
3. The Editor does nothing. No feedback.
4. Click anything: Crash. Windows kills the program.

Additional information: the editor quits as normal when using:
- X close button
- Right-click titlebar -> Close
- System menu -> Close
- ALT-F4

The editor functions seem to work as normal, at least in the short while I've been able to use them in version 1.24.

Confirmed on Ubuntu 12.10.

bernie

Terisa de morgan · 02-14-2014, 04:40 PM

Hi,

I have a problem with 32 bits calibre version 1.24 on Windows 7. At this moment, any time I try to close the editor, it keeps open, and when I try to close the window the answer is always "calibre-parallel not answering", and not waiting for it.

Note: As for now, I see that it closes... after a couple of minutes or more.

AnotherCat · 02-14-2014, 05:26 PM

...and, as to be expected, Win 8.x too.

Re BSODs: For at least the last 12-15 years I have seen as many BSODs as I have seen unicorns in our garden; perhaps unicorns are causal?

BetterRed · 02-14-2014, 06:50 PM

Quote:

Originally Posted by AnotherCat

...and, as to be expected, Win 8.x too.

Re BSODs: For at least the last 12-15 years I have seen as many BSODs as I have seen unicorns in our garden; perhaps unicorns are causal?

Maybe they're not indigenous to your locale

Hmmm - I normally quit programs via Alt+Space/C it seems to work in the editor, as does ctrl/q, as does top right red cross

I cant get to File menu with Alt/F have to use the rodent, click Quit and I get attachment.

BTW : MS nicked the BSOD from OS/2

BR

kovidgoyal · 02-14-2014, 10:44 PM

https://github.com/kovidgoyal/calibr...1e9dedaeb80586

Katsunami · 02-15-2014, 08:49 AM

LOL. You actually forgot to shut down the editor, or was that like somehow removed by accident?

What happened?

kovidgoyal · 02-15-2014, 09:50 AM

One particular code path -- the one triggered by File->Quit -- did not call the editor cleanup code. The cleanup code is responsible for (among other things) shutting down the worker process. The main process was recently changed to wait for the worker process to shutdown cleanly before terminating -- this caused the perceived hang for that code path.

Though if you wait 120 seconds the main process will give up and quit anyway and the worker process will then shutdown uncleanly.

BetterRed · 02-15-2014, 05:08 PM

Quote:

Originally Posted by BetterRed

... I cant get to File menu with Alt/F have to use the rodent...

FWIW - This loss of Alt/F, Alt/E etc seems to coincide with the edit and preview panels getting out of synch, which happens occasionally - my workaround involves terminating and restarting the editor.

If I stumble on a reproducible sequence of actions I'll post a report at launchpad.

BR

Katsunami · 02-22-2014, 01:22 PM

Quote:

Originally Posted by mrmikel

Did you ever see Crocodile Dundee? "Now That's a Knife" How about a blue screen of death? (grin)

Classic scene.

02-14-2014, 02:31 PM	#1
Katsunami Grand Sorcerer Posts: 6,111 Karma: 34000001 Join Date: Mar 2008 Device: KPW1, KA1	Bug: File -> Quit: editor crashes Relevant specifications: Windows 7 64-bit Calibre 1.24 64-bit Removed installation and re-installed (did not remove settings) Steps to take: 1. Open any EPUB book in Editor (I've tested 4. 3 originals, 1 converted from AZW3.) 2. Click File->Quit. 3. The Editor does nothing. No feedback. 4. Click anything: Crash. Windows kills the program. Additional information: the editor quits as normal when using: - X close button - Right-click titlebar -> Close - System menu -> Close - ALT-F4 The editor functions seem to work as normal, at least in the short while I've been able to use them in version 1.24. Last edited by Katsunami; 02-14-2014 at 02:38 PM.

02-14-2014, 03:15 PM	#2
DrChiper Bookish Posts: 907 Karma: 1803094 Join Date: Jun 2011 Device: PC, t1, t2, t3, aura 2 v1, clara HD, Libra 2, Nxtpaper 11	Confirmed. Only, Edit Book does not crash but rather does not respond anymore. I have to manually close the program from pop-up window. BTW: I'm using calibre 1.24 32bit Last edited by DrChiper; 02-14-2014 at 03:18 PM.

02-14-2014, 04:40 PM	#8
Terisa de morgan Grand Sorcerer Posts: 6,233 Karma: 11768331 Join Date: Jun 2009 Location: Madrid, Spain Device: Kobo Clara/Aura One/Forma,XiaoMI 5, iPad, Huawei MediaPad, YotaPhone 2	Problem with Editor and calibre 1.24 Hi, I have a problem with 32 bits calibre version 1.24 on Windows 7. At this moment, any time I try to close the editor, it keeps open, and when I try to close the window the answer is always "calibre-parallel not answering", and not waiting for it. Note: As for now, I see that it closes... after a couple of minutes or more. Last edited by Terisa de morgan; 02-14-2014 at 05:13 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Calibre crashes when I load plugin from file	Cristobal	Devices	14	02-21-2015 10:27 PM
Sigil crashes when trying to add existing file	holdit	Sigil	18	07-16-2013 06:59 AM
Sigil file crashes Sony software	Quiss	Sigil	12	08-14-2012 08:04 PM
Calibre crashes before selecting file to convert.	hambyla	Devices	3	07-22-2011 12:28 PM
Possible bug in 7.4 Tag Editor error	FizzyWater	Calibre	3	06-20-2010 06:11 AM

02-14-2014, 03:15 PM	#3
mrmikel Color me gone Posts: 2,089 Karma: 1445295 Join Date: Apr 2008 Location: Central Oregon Coast Device: PRS-300	Verified with same setup here.

02-14-2014, 03:28 PM	#5
mrmikel Color me gone Posts: 2,089 Karma: 1445295 Join Date: Apr 2008 Location: Central Oregon Coast Device: PRS-300	Did you ever see Crocodile Dundee? "Now That's a Knife" How about a blue screen of death? (grin)

02-14-2014, 05:26 PM	#9
AnotherCat .... Posts: 1,547 Karma: 18068960 Join Date: May 2012 Device: ....	...and, as to be expected, Win 8.x too. Re BSODs: For at least the last 12-15 years I have seen as many BSODs as I have seen unicorns in our garden; perhaps unicorns are causal?

02-14-2014, 10:44 PM	#11
kovidgoyal creator of calibre Posts: 43,850 Karma: 22666666 Join Date: Oct 2006 Location: Mumbai, India Device: Various	https://github.com/kovidgoyal/calibr...1e9dedaeb80586

02-15-2014, 08:49 AM	#12
Katsunami Grand Sorcerer Posts: 6,111 Karma: 34000001 Join Date: Mar 2008 Device: KPW1, KA1	LOL. You actually forgot to shut down the editor, or was that like somehow removed by accident? What happened?

02-15-2014, 09:50 AM	#13
kovidgoyal creator of calibre Posts: 43,850 Karma: 22666666 Join Date: Oct 2006 Location: Mumbai, India Device: Various	One particular code path -- the one triggered by File->Quit -- did not call the editor cleanup code. The cleanup code is responsible for (among other things) shutting down the worker process. The main process was recently changed to wait for the worker process to shutdown cleanly before terminating -- this caused the perceived hang for that code path. Though if you wait 120 seconds the main process will give up and quit anyway and the worker process will then shutdown uncleanly.