Primalscript 2014 Crashing on exit

[sproctor]

I'm running windows 7 64 bit with the 64 bit version of PrimalScript 2014 v 7.0.24. On exit it crashes and after closing that crash dialog I get a 2nd one. I've included the 2 crash details in the other I get them:

Problem Event Name: APPCRASH
Application Name: PrimalScript.exe
Application Version: 7.0.24.0
Application Timestamp: 5334c259
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521eaf24
Exception Code: c015000f
Exception Offset: 000000000006fcec
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: 7e50
Additional Information 2: 7e5040a63f93a72af766704922f07b89
Additional Information 3: 0873
Additional Information 4: 0873689a8967f8447dafd3119cf20bab



Problem Event Name: APPCRASH
Application Name: PrimalScript.exe
Application Version: 7.0.24.0
Application Timestamp: 5334c259
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521eaf24
Exception Code: c0150010
Exception Offset: 000000000006f822
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: 979c
Additional Information 2: 979c9842a4fecc1258a55218f173735b
Additional Information 3: e745
Additional Information 4: e745f064c258ac1f3dd01c9cd36b727a

[sproctor]

Hello? Any comments/suggestions? This is still happening.

[Alexander Riedel]

We have not been able to replicate this. Can you provide more information?
Like what files are open or not? Can you try on another computer so we can isolate if this is your machine or your network environment.
Please also include information about the exact run times installed.

[sproctor]

The problem seems to occur when I save an updated script, it doesn't matter if I am saving it to a network share or locally. If I open a file to look at it and close it I don't get a crash.

I have not had a chance to try installing it on another machine yet and the 2012 version had no issues with this environment. The only thing that has changed on my machine recently are windows/office updates and I was experiencing the issue prior to the last batch of updates I have done as well.

My typical powershell environment is v3, exchange 2010, Quest active roles, Oracle .net, lync and a custom written module.

Any other details you need? I will see about getting a machine to install and test with.

[Alexander Riedel]

Can you please check if it is specific to a certain type of file? Like powershell files yes, batch files no?
Also check if a newly created file shows the same problem.

[sproctor]

I primarily use powershell and ps1 files.

Editing old ps1 files causes a crash.

creating a new ps1 file, works fine, no crash, including editing that new file.

editing old vbs & pl files no crash.

editing old txt file crash.

creating and editing new txt file works fine.

[Alexander Riedel]

Ok, getting closer here.
Check in the status bar if these files differ in encoding please.

If yes, please leave them untouched.

If not, open one of the problem files in Notepad. Save it.
Open it in PrimalScript, modify, save, exit. Does that make a difference?

[sproctor]

The encoding on the old files are ascii, however not all have the problem. The new files are unicode le.

Saving a problematic file with notepad seems to fix the issue.

[sproctor]

I thought we were close, but maybe not. I was just looking at some older code and I think I hit a key by accident and the file thought it was modified. I closed out the app and it asked about saving, I cancelled and still got the double error.

[Alexander Riedel]

Can you do a test for me?

Copy one of the problem files to a flash drive (FAT file system)
Open it from there, modify, save and see if that has an effect.

Thanks.