[
https://issues.apache.org/jira/browse/FLEX-35376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360364#comment-16360364
]
Jed Hatamosa commented on FLEX-35376:
-------------------------------------
Hi Alex,
IM suspecting that there is a possibility that it's a focus issue. Sometimes I
see that the focus will not function. What i meant is the focus sometimes, when
trying to open 2 instances of the app and just use both and perform different
transactions, one of the instance the focus will no longer work. So if like if
there are 2 textfields in the view and you hit tab on the first field the focus
will no longer transfer to the second field. DO you have any idea on possible
cause why the focus/focusmanager will no longer perform the tab functionality?
> 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: details.png, event viewer-1.png, event viewer-1.png,
> event viewer-1.png, 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)
