LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

FileSelectPopupEx causes Stack Overflow when run in CVI 2015 SP 1 on Windows 10 (1607)

Solved!
Go to solution

Hi,

 

when debugging the arrayfile sample within CVI, execution stops with a Fatal Run-Time Error "Stack Overflow" when FileSelectPopupEx() is called - see picture.

The error is not limited to FileSelectPopupEx(), it also happens when Windows' GetSaveFileName() is used.

 

Can someone verify this?

-----------------------
/* Nothing past this point should fail if the code is working as intended */
0 Kudos
Message 1 of 4
(3,770 Views)

No-one? Dang...

-----------------------
/* Nothing past this point should fail if the code is working as intended */
0 Kudos
Message 2 of 4
(3,477 Views)

I just tested here the same example without problems in saving and reading both in ASCII and binary format.

CVI 2015SP1 on Win10 (1511)

 

Are you executing a standard or modified example? I just noted that I haven't that many threads in my program: my threads list shows only 4 entries.



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 3 of 4
(3,473 Views)
Solution
Accepted by topic author CVI-User

An update on this: I happened to capture the error with Visual Studio:

crash.PNG

 

So it's TortoiseGit's overlay icons causing the stack overflow. Increasing the default stack size of the sample is one solution, the other is removing all (?) overlay icon handlers in tgit.

 

Just in case someone else is experiencing this issue.

-----------------------
/* Nothing past this point should fail if the code is working as intended */
0 Kudos
Message 4 of 4
(2,921 Views)