View Issue Details

IDProjectCategoryView StatusLast Update
0024583CommunityOCCT:Samplespublic2014-10-17 16:41
ReporterTimo Assigned Toabv 
PrioritynormalSeverityminor 
Status closedResolutionunable to reproduce 
Product Version6.7.0 
Target Version6.8.0Fixed in Version6.8.0 
Summary0024583: Error message when closing C#-samples
DescriptionI installed OCCT 6.7.0 using the Windows installer. When I open the C#-sample (either WPF or WinForms), open a new document and close the application, a Windows error message appears (see appended image) saying that the application does not work anymore.

My system is Win 7, 64 bit.
TagsNo tags attached.
Test case number

Attached Files

  • c# error on closing.png (22,776 bytes)
  • IE_WinForms.exe.txt (15,972 bytes)

Activities

Timo

2014-01-31 16:06

developer  

c# error on closing.png (22,776 bytes)

Pawel

2014-01-31 16:36

developer   ~0027719

I am also on Win7 x64 with OCCT 6.7.0 (Windows installer) and cannot confirm that behaviour.

abv

2014-02-03 08:37

manager   ~0027720

Hello Timo,

please indicate whether you run Release or Debug configuration, and how you launch the sample (using bat file or from debugger).

This kind of problems often happens due to mixing DLLs bound to Debug and Release variants of CRT in one program. If you run from Debugger, check libraries which are being loaded in Output window, to ensure that they all are either Debug or Release according to your actual configuration.

Timo

2014-02-03 14:16

developer   ~0027731

Last edited: 2014-02-03 14:16

I didn't compile OCCT myself but just started the sample via the Windows Start menu. The same behavior if I start them using the bat files. So it uses the prebuilt Release binaries in directory win32/vc9/bin.

On my system VC++ 2010 is installed.

The other samples (MFC, QT) run without problems.

abv

2014-03-18 16:34

manager   ~0028326

Timo,

Similar problem (exhibiting under VS debugger) has been reported recently on OCC forum: http://www.opencascade.org/org/forum/thread_25909

It is not reproduced on current dev version (Git master branch), could you check on master on your side?

Timo

2014-04-15 14:00

developer   ~0028843

I checked the problem reported on the forum with current master (from 10.04.2014). I couldn't reproduce the problem with win32 (Release and Debug). I didn't check win64 as the description on the form relates to win32.

The problem originally reported by me, I would check as soon as there is a beta setup available for OCC 6.7.1.

Timo

2014-04-17 19:01

developer   ~0028950

The originally reported problem still occurs with OCC 6.7.1 beta using the windows installer without recompilation. When I recompile it with vc10 and start the C# sample then there is no problem. So, it only occurs with the precompiled dlls for vc9. I don't have vc9 installed in order to compile vc9 debug dlls.

I checked still the loaded vc9 dlls with Process Explorer. See appended IE_WinForms.exe.txt

Timo

2014-04-17 19:01

developer  

IE_WinForms.exe.txt (15,972 bytes)

abv

2014-04-29 16:04

manager   ~0029141

I could not reproduce this problem neither on 6.7.1 beta vc9 win32 nor in 6.7.1 release vc10 win64. Actually current master contains some fix related to management of OpenGl resources whose absence could be a reason of this kind of behavior in 6.7.1 (depending on circumstances such as graphic driver). We shall see if it disappears in 6.8.0.

abv

2014-10-17 03:28

manager   ~0033239

Hello Timo, could you please check if this issue is still actual in your environment with OCCT 6.8.0.beta?

Timo

2014-10-17 13:16

developer   ~0033251

The problem is not reproducible anymore with OCC 6.8.0 beta.
Could you say which fix you meant in your comment from 29. April, if it doesn't cost you too much time?
Regards

abv

2014-10-17 15:59

manager   ~0033264

Hello Timo, it is quite difficult to list issues where Open GL resource management have been corrected since they were multiple and interleaved with other changes (massive in 6.8.0). Hope it is not a big need for you. If you agree, I will close the issue then.

Timo

2014-10-17 16:07

developer   ~0033267

Yes, you can close it.
Regards

Issue History

Date Modified Username Field Change
2014-01-31 16:06 Timo New Issue
2014-01-31 16:06 Timo Assigned To => bugmaster
2014-01-31 16:06 Timo File Added: c# error on closing.png
2014-01-31 16:10 Timo Issue cloned: 0024584
2014-01-31 16:36 Pawel Note Added: 0027719
2014-02-03 08:37 abv Note Added: 0027720
2014-02-03 14:16 Timo Note Added: 0027731
2014-02-03 14:16 Timo Note Edited: 0027731
2014-02-03 14:16 Timo Note Edited: 0027731
2014-03-18 16:34 abv Note Added: 0028326
2014-03-18 16:34 abv Assigned To bugmaster => Timo
2014-03-18 16:34 abv Status new => feedback
2014-04-15 14:00 Timo Note Added: 0028843
2014-04-17 19:01 Timo Note Added: 0028950
2014-04-17 19:01 Timo File Added: IE_WinForms.exe.txt
2014-04-17 19:02 Timo Assigned To Timo => abv
2014-04-17 19:02 Timo Status feedback => assigned
2014-04-29 16:04 abv Note Added: 0029141
2014-04-29 16:04 abv Target Version 6.7.1 => 6.8.0
2014-10-17 03:28 abv Note Added: 0033239
2014-10-17 03:28 abv Assigned To abv => Timo
2014-10-17 03:28 abv Status assigned => feedback
2014-10-17 13:16 Timo Note Added: 0033251
2014-10-17 13:16 Timo Assigned To Timo => abv
2014-10-17 13:16 Timo Status feedback => resolved
2014-10-17 15:59 abv Note Added: 0033264
2014-10-17 16:07 Timo Note Added: 0033267
2014-10-17 16:41 abv Status resolved => closed
2014-10-17 16:41 abv Resolution open => unable to reproduce
2014-10-17 16:41 abv Fixed in Version => 6.8.0