flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Harui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-35376) Desktop application created for Windows is crashing unexpectedly
Date Fri, 19 Jan 2018 09:01:00 GMT

    [ https://issues.apache.org/jira/browse/FLEX-35376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331947#comment-16331947
] 

Alex Harui commented on FLEX-35376:
-----------------------------------

I doubt AIR is corrupted, but you could always uninstall and reinstall it.

Depending on how you plan to deploy the app, you might try making a 64-bit version instead
of 32-bit.

The event viewer.png is hiding information about the crash which might lend a clue.

I'm out of time for today.  You could try commenting out some portion of the app to see what
is causing the problem.  If the crash occurs when a new instance is starting up, then try
commenting out bits of startup code.

> Desktop application created for Windows is crashing unexpectedly
> ----------------------------------------------------------------
>
>                 Key: FLEX-35376
>                 URL: https://issues.apache.org/jira/browse/FLEX-35376
>             Project: Apache Flex
>          Issue Type: Bug
>    Affects Versions: Apache Flex 4.16.0
>         Environment: Windows 10
>            Reporter: Jed Hatamosa
>            Priority: Major
>         Attachments: event viewer.png, exe has stopped working.png, my machine.png, runtime
error.png
>
>
> We have an air application that supports multiple instances (can run multiple windows
app). Recently we are experiencing a crashing issue (Please see attached file). When trying
to test in other OS like Windows 10 pro, its working fine. But for some like Windows 10 Home
it will crash. I have also tested running the app in Mac OS and it is working fine. 
> We can replicate the issue if we are going to run multiple instances of the app, then
we login on both instances, then do some parallel transactions on both instances until we
get the error at some point. 
>  
> We have also tried running in debug mode but I cannot replicate any null exception issue
and it will just show the not responding issue. SO it's really hard right now to pin point
where the issue is and what is causing the issue. Maybe you can help us give some more info
on where and why this is happening. Is this a system issue? IS this something in the code
?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message