[
https://issues.apache.org/jira/browse/FLEX-35376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331901#comment-16331901
]
Alex Harui commented on FLEX-35376:
-----------------------------------
Well, first you need to verify it is a running-out-of-memory issue.
If it is, IMO, whether you build your app in Flex on AIR or some other
language, if you use up too much memory you will run out of memory. Flex/AIR
might use more memory in certain situations than other languages and runtimes,
but probably not a lot more, so if you keep making new instances you will
eventually run out of memory.
AIR has a different garbage collection subsystem than other runtimes like Java
so you might need to implement some strategies to make sure you don't flood the
GC subsystem, but again, first you have to prove that memory is the issue.
> 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, 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)
