Ticket #21 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

09-014 GLCC UO in PRO/II 8.3

Reported by: michelpons Owned by: michaelhalloran
Priority: major Milestone: Refactoring
Component: COLoggers Version: 1.08.2
Keywords: Cc: michaelhalloran

Description

De: Michel Pons [technologyofficer@…]
Envoyé: Wednesday, June 24, 2009 10:50 PM
À: 'Ahsan Akhtar'
Cc: 'Michael Halloran'
Objet: COLTT 09-014 Debug and crash for GLCC in PRO/II

Pièces jointes: proii_062409_223724.log

Ahsan,

I have a scenario showing a strange behaviour on COLTT 1.08.02. It involves a UO PMC (GLCC) and PRO/II 8.3. Without COLTT enabled on GLCC UO, the calculation of the UO does not go well and I wanted to look at the log in order to figure out what was going on.

However enabling COLTT 1.08.02 on GLCC leads first to a debug assertion error then a crash a bit after instantiating the GLCC UO within the PRO/II flowsheet.

In fact I have two crash messages as follows:


Microsoft Visual C++ Debug Library


Debug Assertion Failed!

Program: C:
SIMSCI
PROII83
Bin
PROII.EXE

File: d:
program files
microsoft visual studio 9.0
vc
atlmfc
include
atlcomcli.h

Line: 154

Expression: p!=0

For information on how your program can cause an assertion

failure, see the Visual C++ documentation on asserts.

(Press Retry to debug the application)


Abandonner Recommencer Ignorer


I selected « Ignore » and got :


Exception Detected


Exception code 0xc0000005: EXCEPTION_ACCESS_VIOLATION

The thread tried to read from or write to a virtual address for which it does not have the appropriate access.

Select Cancel to debug or OK to save the copy and quit.


OK Annuler



Exception Detected


Exception code 0xc0000005: EXCEPTION_ACCESS_VIOLATION

The thread tried to read from or write to a virtual address for which it does not have the appropriate access.

Select Cancel to debug or OK to save the copy and quit.


OK Annuler


There is a short log created. It is attached. I have numbered this issue 09-014. Let me know if you need Visual Studio 2008 installed in the VM dedicated to this issue.

Best regards

Michel

Attachments

proii_062409_223724_V10802.log (2.3 KB) - added by michelpons 11 years ago.
Log file obtained with COLTT 1.08.02
proii_102409_142230_V10803.log (2.4 KB) - added by michelpons 11 years ago.
Log file obtained with COLTT 1.08.03
proii_110609_112126.zip (72.9 KB) - added by michelpons 11 years ago.
Zipped log file obtained with COLTT 1.08.4

Change History

Changed 11 years ago by michelpons

Log file obtained with COLTT 1.08.02

comment:1 Changed 11 years ago by michelpons

I have used COLTT 1.08.03 (Build Oct 19, 2009) on the combination used within the scenario documented. I have noted that the debug assertion failure message has disappeared with 1.08.03 while PRO/II is still crashing after selecting the GLCC UO and trying to bring it into the flowsheet. I have attached the log file obtained with COLTT 1.08.03 enabled on the GLCC UO (proii_102409_142230_V10803.log).

Changed 11 years ago by michelpons

Log file obtained with COLTT 1.08.03

comment:2 Changed 11 years ago by michaelhalloran

  • Owner changed from Michael Halloran to michaelhalloran
  • Status changed from new to assigned

Looks to be the same as #4 and #17 from the log. Hope to fix shortly.

comment:3 Changed 11 years ago by michelpons

  • Status changed from assigned to closed
  • Resolution set to fixed
  • Milestone set to Refactoring

I have re-tested the case with COLTT 1.08.4. There is no crash of PRO/II anymore with the scenario used and a complete log file is obtained (proii_110609_112126). So I consider the defect as fixed.

Changed 11 years ago by michelpons

Zipped log file obtained with COLTT 1.08.4

Note: See TracTickets for help on using tickets.