Flowcode v8 shutting down

[billduck]

I was wondering if anyone is experiencing FC starting and immediately shutting down. I am.
I tried uninstalling and re installing. Did not work. Help!
This is one of the few diversions I have during the pandemic.

[medelec35]

Hi billduck, have you updated V8 with 8.2 patch?
Can you remember what target device you used last?
One thing to try:
1) Make sure Flowcode is not running
2) Run Regedit, Only delete

Code: Select all

HKEY_CURRENT_USER\Software\MatrixTSL\FlowcodeV8

Nothing else as deleting windows system files will stop pc from working.

[billduck]

Cool. It has worked. You da man, as usual!

[medelec35]

Your're welcome,
Glad it fixed the issue.
Thanks for updating us.

I assume was the registry rather than patch?

[billduck]

It was the regedit modification.
I routinely check for updates. was the 8.2 patch included there?

[medelec35]

Thanks for confirmation.

I routinely check for updates. was the 8.2 patch included there?

No, you will need to manually update with the patch if you have not got v8.2?
What version have you got?
I have got 8.2.2.15

[beneee]

I am now having the problem of it just closing, this has happened when I am in the middle of changing things, running a sim, programming and just sitting in the background doing nothing..
I have been working on a 12F1501 project.
I have changed the graphics to software and it is still closing - no prompt if I haven't saved, just closes.
I am running 8.2.2.15
Only been happening the last couple of days.

Is there any update I have missed?

Thanks
Ben

[Steve]

Hi Ben,

The last time we had a problem like this, we think it was linked to a recent Windows update. Has Windows updated any core components recently? Or have there been any other changes on your PC (e.g. new antivirus or firewall)?

There is a thread here which discussed a similar problem that might offer some pointers:
https://www.matrixtsl.com/mmforums/view ... 1&start=25

And if that doesn't help, could you tell us more about the problem - e.g. does it always happen or is there any specific action that triggers the shutdown? And does it also happen in Windows safe mode?

If Flowcode appears to work in safe mode, then it's likely to be another application on your PC that is interfering with Flowcode. You should check any logs in your antivirus/firewall/etc to see if these are doing anything. Also, try adding Flowcode's exe file to the exceptions of these programs.

[beneee]

I have just checked and my has not had any updates for a couple of weeks.

It just crashed again in a sim - it got slower and slower then froze for a few seconds then closed

I have got entries in the Application log / Event viewer from fc8 crashing yesterday, here are two of them - most are just about the same.

Ben


_Windows Error Reporting_

Fault bucket 1439326493891649642, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FlowcodeV8.exe
P2: 8.2.2.15
P3: 5e593fd7
P4: ntdll.dll
P5: 10.0.17763.1039
P6: 5c18dfc8
P7: c00000fd
P8: 00058bd5

--------------------------------------

_Application Error_

Faulting application name: FlowcodeV8.exe, version: 8.2.2.15, time stamp: 0x5e593fd7
Faulting module name: ntdll.dll, version: 10.0.17763.1039, time stamp: 0x5c18dfc8
Exception code: 0xc00000fd
Fault offset: 0x00058bd5
Faulting process ID: 0x17784
Faulting application start time: 0x01d69bdf0a3ab9a5
Faulting application path: C:\Program Files (x86)\Flowcode v8\FlowcodeV8.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: 4aea3bd7-e3b3-4bc6-868d-fb8bfa6620f1
Faulting package full name:
Faulting package-relative application ID:

crash.PNG (20.99 KiB) Viewed 4686 times

[Steve]

Thanks for the info. Please send me the program you were simulating and I will try to replicate the error.

[beneee]

Here you go.

Thanks
Ben

Small.fcfx

(23.36 KiB) Downloaded 158 times

[Steve]

Thanks, Ben.

I have been able to confirm and replicate your crash, and I think I've found a workaround. If you set the 4 PWM objects' "Representation" properties to "Digital", the problem does not occur.

The problem is Flowcode is running out of memory during the execution of this particular program and seems to be linked to the calls to change the duty cycle. If you run the simulation you can see Flowcode's memory allocation increasing in Window's Task manager.

Some partial good news is that the problem does not seem to be present in the next version of Flowcode and both "Analogue" and "Digital" representations work ok.

Regards,
Steve.