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

Crash on Preview #139

Open
achapin opened this issue Mar 10, 2015 · 5 comments
Open

Crash on Preview #139

achapin opened this issue Mar 10, 2015 · 5 comments

Comments

@achapin
Copy link

achapin commented Mar 10, 2015

If I open a preview for a file, close the preview windows, and then click the preview button again, Flump crashes.

@tconkling
Copy link
Owner

I've seen this as well - it's actually the Flash runtime crashing, as opposed to a logic error in the Flump exporter itself. That said, I'm not currently able to reproduce it. Are you on a Mac or Windows? What version of AIR do you have installed?

@achapin
Copy link
Author

achapin commented Mar 12, 2015

I'm on OSX 10.9.5, Air Version 16.0.0.245

On Thu, Mar 12, 2015 at 3:08 PM, Tim Conkling [email protected]
wrote:

I've seen this as well - it's actually the Flash runtime crashing, as
opposed to a logic error in the Flump exporter itself. That said, I'm not
currently able to reproduce it. Are you on a Mac or Windows? What version
of AIR do you have installed?


Reply to this email directly or view it on GitHub
#139 (comment).

@tconkling
Copy link
Owner

I wonder if it's based on the number of items, or size of textures, in your project? That's basically the setup I have, but I'm not seeing these crashes for the last number of AIR versions

@achapin
Copy link
Author

achapin commented Mar 13, 2015

I think it has to do with the windows closing, because if I open a new
source directory and preview a new FLA file, it doesn't crash. I'd send the
source files that are causing the issue, but I don't have the rights to do
that.

On Thu, Mar 12, 2015 at 4:32 PM, Tim Conkling [email protected]
wrote:

I wonder if it's based on the number of items, or size of textures, in
your project? That's basically the setup I have, but I'm not seeing these
crashes for the last number of AIR versions


Reply to this email directly or view it on GitHub
#139 (comment).

@tconkling
Copy link
Owner

It sounds like it may have to do with how we're disposing of a stage3D context or something. Can you run flump in the debugger to see which call is actually triggering the crash?

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

2 participants