1.8 RC5 crashes when closing image Windows 7

[Juan Conejero]

I wouldn't have thought that closing an image would have changed that much between versions

Lots of apparently trivial things have changed in 1.8.0. I have rewritten about a 70% of the whole platform.

There's something in your Windows OS that is interfering in a very strange way with this version of PI. I definitely cannot reproduce it on *any* of our development machines running Windows (and I have tried hard). Could you try with a different PC? Also, which antivirus software are you using?

[Komet]

"Could you try with a different PC? Also, which antivirus software are you using?"

I am using AVG and this is the only 64bit Win7 machine I have.  (Recently upgraded to 64bit due to your plans to go just 64bit (it is quicker though!  )  It isn't just me though is it as the first user on this thread has the same problem.

V1.7 ran flawlessly on this machine and would go back to it except that it appears that the Batch Preprocessing is missing from the 1.7 on the download site. Is this right? (Great script BTW)

Every other piece of software I am running is operating correctly. Its only closing modified images in PI that is the problem.

[Juan Conejero]

This problem could be hardware-related. have you overclocked your machine, by chance?

[Komet]

No - totally default.

[Juan Conejero]

I'm writing this from a laptop with Windows 7 x64, where I've just made another attempt at reproducing these problems ... without success.

BEX errors are related to buffer overruns, which may be caused by memory access problems (a faulty DIMM module for example). If you Google for this problem, this is the first result. As you see, BEX crashes may affect any applications, including explorer.exe (and in this case the whole operating system gets blocked).

This is another example with the Excel application, and this one with the NVIDIA control panel, both very similar to what you're experiencing with PI. You may find hundreds of similar cases. Maybe some of the answers given in these examples may help you.

[Juan Conejero]

I have some news. After a lot of testing, I have managed to reproduce this BEX64 crash:

http://pixinsight.com/forum/index.php?topic=5297.0

But it only has happened when closing the PI Core application. Note that the faulting module is MSVCR110.dll. Interestingly, this is the Microsoft C Runtime for Visual Studio 2012

I have managed to fix the problem with the DarkStructureEnhance script. There is a bug in the PI Core application for Windows, which I'll fix next week. I'll release also a new version of the DSE script. By chance, this bug rises a BEX64 error, but in this case the error is "correct" (there is an invalid execution attempt as a side effect of the bug; that's why the problem is 100% reproducible), and is unrelated to the problem you're experiencing.

Finally, this document on Microsoft's website is a bit technical, but it provides a lot of useful information about BEX errors and DEP:

http://technet.microsoft.com/en-us/library/cc738483%28WS.10%29.aspx

[Komet]

Having read about many BEX errors and DEP (which doesn't appear to be applicable to a 64bit system) I was left totally in the dark to be honest.

I was trying to get a definitive series of events that causes the crash but each time it could be slightly different - the number of steps doing something etc.

I then read about starting PI holding the Ctrl key to reset it. Now as I haven't actually customised PI in any way I didn't think it would do anything but any port in a storm eh?

It appears that this may have done the trick. I can repeat the procedures I was doing before which caused the crash every time but I have not had a single instance of it as of yet. As I said I have not changed any of the preferences in PI in 1.8 or 1.7 previously. It was running in default mode so what the reset did - well perhaps you know as I obviously don't.

I'll see how it goes but at the moment it appears fine. Here's hoping ........

 

[Komet]

Spoke too soon ... its happening still. 

Gone back to 1.7 as 1.8 is unusable. I cannot believe that closing an image without crashing the program can be that much of a problem.

[Juan Conejero]

I am very sorry to hear that. I really don't know how to help you, as I am unable to reproduce the problem you're experiencing on any machine running Windows that I have access to.

I need to know if more users are experiencing the same problem with PI 1.8.0 RC5: The application crashes when closing an image window.

I need both positive and negative reports.

[Andres.Pozo]

This has never happened in my computers. Both are Win 7 x64 machines with Core i7 processors, 8GB of memory.

[Christoph Puetz]

I have Win 7 professional x64, Intel Dual Core, 8GB mem, Symantec Endpoint Protection Anti-Virus/Firewall,
cpu overclocked by bios.
I tried the steps as described in your report.

But I can not reproduce this.

Hint: Did you check your ram/memory for errors ?
Here is described how to do: http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

Just to be sure, you should also check the integrity of your filesystem where PI stores its swap files and
the system disk (where the windows swap file lies).
http://support.microsoft.com/kb/2641432

[Jordi Gallego]

Juan
I have Win 7 professional x64, Intel Quad Core, 8GB memory in my laptop.

I cannot reporduce the problem

Regards

[Komet]

The problem is only apparent in the 64bit version of 1.8 I am trying the 32bit and that seems fine (up to now).

I have already run Memtest without issues. The install of Windows7 Pro N is new (and done only because of the end of 32bit support for PI ironically). It runs faultlessly.

1.8 64bit can run any process without problems at all so it can hardly be a memory problem anyway. It only happens just closing a modified image. The image closes and then a few seconds later that error message comes up. There is this pause .... what is PI doing just after an image is closed?

[RoStm]

Hi Juan,

>I need both positive and negative reports.<

I'm running PI 1.8 RC5 on WIN 7 Home Premium x64, i7-3770, 16 GB RAM and tried to reproduce the described crash.

No occurence so far, I could not force such a crash.

Regards,
Rolf

[sreilly]

My experience with this problem is during the use of the BackgroundEnhance script. I've attached both the screen dump and the full text of the error message. I haven't seen this before but then I don't often use this script.

My equipment:

Windows 7 Pro 64 bit fully updated
Asus P8Z68-V-PRO main board w/AMI Bios 3203
Intel Core i7-2600K CPU @3.40GHz
Corsair CMZ16GX3M4A1600C9 RAM x 4 = 16 GBs total RAM
NVidia GeForce GTX 550 Ti Video card
OCZ-Agility3 256GB SSD
Western Digital ST31000528AS 1 TB Hard drive