Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ozengine sometimes crashes with an assertion that failed #239

Open
jaymelbe opened this issue Oct 6, 2014 · 7 comments
Open

ozengine sometimes crashes with an assertion that failed #239

jaymelbe opened this issue Oct 6, 2014 · 7 comments

Comments

@jaymelbe
Copy link

jaymelbe commented Oct 6, 2014

Hello, thanks for the good job and all the new updates.
However I am facing an issue with the latest build (4127).
I am running it on Windows 8.1 and it is a 64bit version of Mozart2. Sometimes while everything "seemed" to be ok.. I press a button of my application (which usually works) and then get this crash:

Assertion failed!

Program: C:\Users\jaymelbe\Dropbox\redist\bin\ozengine.exe
File: C:/projects/mozart2/vm/boostenv/main/../../vm/main/runnable.hh, Line 44

Expression: from._last == from._list.begin()

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

Have anyone already faced that? Any idea what it means?
Thx for help!

@jaymelbe
Copy link
Author

jaymelbe commented Oct 6, 2014

I have made some tests with the same code, but using the build 4105 and I never get this issue.
So it should have been added with the recent fixes

@jaymelbe
Copy link
Author

jaymelbe commented Oct 9, 2014

Nobody able to explain what it is this file about? And why is the assert failing:

assert(from._last == from._list.begin());

I really need help please.

@eregon
Copy link
Member

eregon commented Oct 9, 2014

Looks like the intermediate state (used to handle non-idempotent code) gets corrupted.
But I guess only @sjrd knows that well.
Is it expected to have asserts enabled on Windows releases?
@jaymelbe Could you give the commit range?

@jaymelbe
Copy link
Author

The build from Sept 24 is ok.. so I guess it is the 6 latest commits that may have corrupted something.

@sjrd
Copy link
Member

sjrd commented Oct 12, 2014

git bisect anyone?

@sjmackenzie
Copy link
Member

@jaymelbe
Copy link
Author

I don't use git but I will try to do that as soon as possible.
The problem is that it happens randomly.. Hard to find a code that always trigger this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants