This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Sometimes apphang Ple4Win.exe
03-03-2015, 05:43 PM, (This post was last modified: 08-04-2015, 08:40 AM by shaswin.)
#1
Sometimes apphang Ple4Win.exe
Affected version: Ple4Win Professional version 4.3.0 build 14120 / 4.3.1 build 15032

When one closes a project file by closing <red right-top cross button in the title bar> the Ple4Win program will close. If you have Windows File Explorer listed/opened in the taskbar, Windows will return back to the directory in Windows File Explorer. When one opens then another project file within a few seconds the following warning may appear:

   

   

This issue is not always reproducible.
I have attached the Windows Error Reports of two Ple4Win crashes.

The version build number in P2 in the logbook should be 4.3.0.14120 in this case.
Used operating system: Windows 7 Pro SP1 64-bit (all .NET Framework updates has been installed).


Attached Files
.zip   Windows Error Reports.zip (Size: 3.55 KB / Downloads: 2)
Reply
19-05-2015, 12:27 PM,
#2
RE: Sometimes apphang Ple4Win.exe
Thanks for reporting this. It is not a situation we encountered before.

I am not sure about what we can do about this. The error logs do not give a useful indication on what might be the cause of the crash. Maybe it is a timing problem, Windows might be still working on closing the program in the background (or doing garbage collection).

From your post I understand that this issue does not occur if a bit of time is allowed to pass between program closure and the next program start. So a bit of patience is the best workaround here Wink
We will look into it, and try to reproduce it here.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)