Been working on an iPad book app in FlashBuilder 4.6. Early on there were some performance issues with iPad1/3 until learning about GPU rendermode and setting the StageQuality to low. These helped immensely.
However, recently the app starting crashing on startup - only on iPad1. For example page 1 of the app which had worked weeks ago would now crash. After more research, it seemed that the static references to all the page classes that were put in the ViewController were the issue. They seemed to be overwhelming the memory. When I put only a static reference to page1 in the VC it worked. And then in page 1 were static references to page 2 or 3. Or whatever pages it might link to. Now, after reworking the 70 other pages to only static reference the pages they need, it is crashing again.
My question is this, if I have page 1 with a static reference to page 2 and 3. And each of those have references...all down the line to say page 70, are all those in essence getting loaded into memory at startup?
The bigger question is how best to manage the memory of an AIR app that will have ~ 120+ "pages" or views in MVC parlance? Ideally, I only want the dynamically created view in memory but don't think it's working.
I've read the other posts here and was thinking about loading/unloading swfs that have references to needed classes via ApplicationDomain.
One interesting thing noticed is this. When launching the app in the debugger, it traces out terminated and the app quits. However, when double clicking the iPad home button, it shows the app still running. Not sure why that is?
Pardon the lengthy description.
Any and all help would be appreciated.
Thanks,
MTG
Related
My vuejs nuxt portfolio(https://gunjankadu.com/)is not opening on ios phones but working flawlessly on all other devices. On IOS devices only a red spinner is shown and nothing more.
What can be done?
A script "tag.js" took time to load, which I have currently disabled but still not working.
I had a look on your application and found out two problems.
First was about regular expressions, It seems Safari doesn’t support look behind yet. One alternative would be to put the / that comes before in a non-captured group, and then extract only the first group (the content after the / and before the #).
/(?:\/)([^#]+)(?=#*)/
And second is about The minimal-ui viewport property that you can find out more here
Look at all your js/vue files especially in store. And see if any variable used is not imported. Nuxt in SPA mode doesn't detect those kind of errors and surprisingly the UI gets stuck on loading only on iOS. Very weird but scratched my brain over it for a day.
I created a webapp in Vue several months back and have been using it for some time. I've used it on Android, iPhone, Mac, Windows, and all was good in the beginning, however a couple of months back, I began noticing that the page would sometimes load on iPhone, and sometimes not. It worked perfectly fine on every Android I've tried without issue, works on Mac and on Windows, though iPhone seems to be hit or miss (haven't tried it on any other iOS/iPadOS devices), and I have no idea where to start. I know this doesn't give a lot of information to begin with, but I'm not sure how to even begin debugging this. What I have tried so far:
Resetting cache - did not fix
Using various browsers - blank page across Safari, Chrome, in private/incognito modes and normal modes
Tried different iPhones - would work without issue on some, but not on others
I have not touched the Vue config file, is there some support issue between specific iOS versions and Vue that I'm not aware of?
Again, I know there's not much detail provided other than "It doesn't work", but I honestly don't know what else to try or what information I might be able to use - if there is something additional I need to provide, let me know and I can update the post with the information.
I have an asp.net MVC 5 framework that runs a bunch of sites and we have an issue where as the site runs for a few days(sometimes even hours), it begins to error about being able to load views (The partial view ~/Views/Comment/ExtraHeaders.ascx was not found or no view engine supports the searched locations the following locations were searched).
The error also occasionally says "The file '/Views/Cobalt/Shared/Error.aspx' has not been pre-compiled, and cannot be requested" This view file is also definitely there
We do precompile the views before deploying. This error persists after an app restart, but goes away when redeploying the code. Any ideas about how to debug the underlying problem?
I am going to try and do a byte by byte comparison of every file the next time it happens to see if maybe some corruption is happening?
I had a perfectly well running asp.net mvc application and I was debugging message sending via SignalRand I decided to stop debugging and went to edit some code. However, there was an error saying something about IIS termination and whether I want to do that because something (I assume - the application) cannot be stopped. (I am really sorry, but I didn't read it at the time). So now I try to relaunch my program and it just won't open. The website is trying to be opened but the loading circle in chrome just kept on spinning forever.
What I tried to do was:
1. restarted VS - didn't help
2. restarted PC - didn't help
3. created a new project, brought all files to it and launched it and it worked!
So then it worked for ~10 minutes or so and then just stopped again (this time no error message or anything). I tried changing a port in the settings of the project. Didn't work. Tried changing back and it launched successfully. For a minute or so... :(
So finally, I tried putting a break point right at the
public class MvcApplication : System.Web.HttpApplication
{
protected void Application_Start()
-> {
The breakpoint was hit, it successfully passed the next line
RouteTable.Routes.MapHubs();
and just disappeared at
AreaRegistration.RegisterAllAreas();
Many times I tried and it always disappears at the same location. Going deeper is not an option since this is system method. I suspect something can be problematic with that, but I am not experienced with much configuration of asp.net.
P.S. many times VS was acting strange and even tho I set the breakpoint at the place I marked above, it showed the breakpoint with a message that it won't be hit because the source differs from the current code (But I didn't change a thing since before the very first crash! The only place I modified a few symbols at was at MyHub.cs which is an extended class for a Hub for SignalR)
Lastly, I tried deleting everything from bin folder so it got fully rebuilt, but without any success to revive my application.
What could be a possible problem, maybe someone had anything at least similar to this? Or maybe someone would be kind to help me at choosing better keywords while searching in google because "IIS termination" and "AreaRegistration.RegisterAllAreas(); not working" didn't bring me much :(
This is a known bug: https://github.com/SignalR/SignalR/issues/1335.
We have been unable to successfully reproduce this issue on our servers. We've seen that using a different web server will resolve the issue. If you're able to post a reproduction project to the linked Issue, chances are it will be resolved promptly.
Apparently, the solution I marked isn't the exact thing that helped me. This link was the thing that miraculously helped me and I was able to finally get back to work. However, I found the winning link because of N. Taylor Mullen, so he deserves the full credit :) But letting others know if anyone comes to this question :)
I have developed a monodroid application with several activities.
Occasionally, the wrong activity is shown first, as opposed to the one with "MainLauncher=true" set.
Also, occasionally I get a dialog stating "Could not determine activity to run because the generated manifest could not be found?
I occasionally see the wrong activity on startup.
I think this generally seems to be when I haven't changed any code and try to restart my application for a second debugging session.
I think what happens in this case, it that Android tries to restart my application on the page/Activity where I last left it. This situation also happens when the app is in general use - so it's good practice to write your code so that the app works in this situation (e.g. using the saved instance state bundle)