PrimalScript 2011 crashing

Fri Feb 17, 2012 8:09 am

I double clicked on one of the variables in the script. Not exactly sure which one. This happened when I had multiple vbscripts open and one of the other scripts was modified with and not saved. Does that help?

Post by **Alexander Riedel** » Fri Feb 17, 2012 8:13 am

Not really

I'd need to know exactly what you clicked on.
I really can't make that crash happen here no matter what I do. Whatever else you have open has probably little meaning.

Post by **Alexander Riedel** » Fri Feb 17, 2012 10:37 am

I posted another test build (165)

Post by **dominik.ecke** » Mon Feb 20, 2012 11:17 pm

hi Alexander,

a new crash, this time with ScriptParse.dll (intentionally I assume...).

I again switched back to PrimalScript, clicked into it (maybe double-clicked). No specific spot was clicked...

Just to emphasize it again: Reproducing is near to impossible. I can open up the same script again and work with it for hours without a crash, and suddenly it crashes. And this happens on many different scripts, so not only on specific ones.

P.S.: BBCode does not like me today

Code: Select all

Faulting application name: primalscript.exe, version: 6.0.165.0, time stamp: 0x4f3ef0c8
Faulting module name: ScriptParse.dll, version: 3.4.7.0, time stamp: 0x4f3ef068
Exception code: 0xc0000005
Fault offset: 0x000381fc
Faulting process id: 0x8d4
Faulting application start time: 0x01ccf0976870fb75
Faulting application path: C:Program FilesSAPIEN Technologies, IncPrimalScript 2011primalscript.exe
Faulting module path: C:Program FilesSAPIEN Technologies, IncPrimalScript 2011ScriptParse.dll
Report Id: c1988817-5c8d-11e1-8fa0-001999a6f128

Code: Select all

Faulting application name: primalscript.exe, version: 6.0.165.0, time stamp: 0x4f3ef0c8
Faulting module name: ntdll.dll, version: 6.1.7600.16915, time stamp: 0x4ec49caf
Exception code: 0xc0150010
Fault offset: 0x0008167f
Faulting process id: 0x8d4
Faulting application start time: 0x01ccf0976870fb75
Faulting application path: C:Program FilesSAPIEN Technologies, IncPrimalScript 2011primalscript.exe
Faulting module path: C:WindowsSYSTEM32ntdll.dll
Report Id: c2c6a3f9-5c8d-11e1-8fa0-001999a6f128

dominik.ecke2012-02-21 07:39:40

Post by **Alexander Riedel** » Tue Feb 21, 2012 10:11 am

No, unfortunately crashes are never intentionally.
I will look at that location but the other code for the ntdll location worries me a bit. The web is full of questions about that Exception code and just as with the other crash it so far looks like the compiler is the culprit. which is why it is so hard to pin down.

We keep working on it until we nail it down.

Post by **dominik.ecke** » Mon Mar 05, 2012 1:23 am

just wanted to tell: currently using build 167.
So far did not have any more crashes... let's hope it stays that way

Post by **Alexander Riedel** » Mon Mar 05, 2012 2:23 am

Thanks for the heads up. You and me both!