PostView crashes on second instance of vector plot
issueid=447 10-04-2011 08:59 AM
Moderator
PostView crashes on second instance of vector plot

Hi Steve,

PostView crashes after the following sequence:

1) Load a plot file
2) Create a vector plot (any vector variable)
3) Delete the vector plot (click on the X button in the Model Viewer)
4) Create a vector plot again (any)

At this point PreView crashes (this has been consistent).

Best,

Gerard
Issue Details
Issue Number 447
Project PostView
Category Unknown
Status Fixed
Priority 1 - Highest
Affected Version Unknown
Fixed Version (none)
Users able to reproduce bug 0
Users unable to reproduce bug 0
Assigned Users maas
Tags (none)




10-06-2011 10:33 AM
Lead Code Developer
Hi Gerard,

It's not doing that for me. What version are you using?

Steve.

10-06-2011 11:59 AM
Moderator
Hi Steve,

I am using PostView 1.3.5.2511, on the Mac.

Best,
Gerard

06-18-2012 11:32 AM
Lead Code Developer
Hi Gerard,

I'm cleaning some old posts. Is this still an issue for you?

Thanks,

Steve.

06-26-2012 02:00 PM
Moderator
Hi Steve,

Yes, this is till an issue. I just tried it with the latest version of PostView and was able to reproduce the crash as originally described.

Best,

Gerard

06-26-2012 02:27 PM
Lead Code Developer
Strange. PostView is not crashing for me (at least the WinXP version). Are you looking at a specific vector field? Does it happen with any file? Can you send me a file that is crashing for you?

Thanks,

Steve.

06-26-2012 04:30 PM
Moderator
Hi Steve,

It crashes on the Mac but not on Windows. When I debug it, the crash occurs in
Code:
int CExprChoice::value(int n)
, at the statement
Code:
assert(i<size());
. It reaches this statement from
Code:
CVectorProps::Update
. Basically, it fails the assertion.

I get the error with any file that i use, e.g., the cnt02 problem in the test suite.

Best,

Gerard

06-26-2012 06:42 PM
Lead Code Developer
Thanks, that helped in finding the bug. This should be fixed now.

Cheers,

Steve.

06-27-2012 09:15 AM
Moderator
Thanks, the bug is indeed fixed.

Best,
Gerard

+ Reply