Call for action on current crashing/freezing issue

[Resmi9793]

@TetsuoWallace Welcome to the thread. Any chance you can get some new diags as per my original post?

[Resmi9793]

@EA_UltraSlide @EA_HighCommand  I see you have both been active today...  Is there anything you can share from the developers about what's going on here?

[QuimSWGoH]

@GladOS-013 Men, you are not understanding that the main problem of thiese freezes and crashes is the communication. I think is happening in enough devices to worth it an announcement in the main forum. Is happening in several Android and iOS devices and is happening in all emulators (BlueStacks, MeMu, Nox, etc.), happened in streams of important youtubers like "AhnaldT101" (3 times) and "Its Just Ian", I don't care if is not happening in your device, also is not happening in my iPhone SE, but there is at least 40 reports of the same bugs with maybe 15 different devices and several repetated devices, so it deserve an announcement and this lack of communication is unacceptable, also I don't care if this forum not support the emulators, the emulators are important for this game, and is happening in a lot of phone devices, tablets, not only emulators, is happening in all devices, currently I cannot play in BlueStacks because when you open the app first of all is needed try between 3 and 10 times to login, sometimes crash between 3 and 5 consecutive times at the beginning before you get start to use the app, and when you get it only delays 5-10 minutes to freeze or crash again, is unplayable in this moment. So there is not any excuse to accept the lack of communication, this is another big black moment for Capital Games.

[Resmi9793]

Time for an update on my previous investigations (https://answers.ea.com/t5/Bug-Reports/Call-for-action-on-current-crashing-freezing-issue/m-p/9332282...)...

Since then, I have been working on the principle that this issue is all about available RAM.  The updated version of the game needs more memory than before and fails in the way that is well-documented in this forum when it can no longer allocate what it needs (dodgy graphics then freeze).  If that theory is true, you should be able to increase the amount of time the application runs by increasing available RAM.  Sadly, there is only one reliable way to do this...  Uninstall other apps.  These often run liitle bits of code in the background even when you have not started the app (e.g. to check for notifications).  Just killing background processes using one of those optimizer tools is no good - it will start up again.

I am lucky...  I have a phone for all my everyday apps, so can use my tablet just for games and entertainment.  That means I could uninstall a lot of software on the tablet.  Doing this has reduced my crashes from several an hour down to about one a day.  However, this won't be a viable option for many.  Is it really reasonable to ask your users to install only your game on the device?  I think not...

The real fix is to slim down the game and look for those hanging references that are leaking memory to the point that the game crashes.

As always, I would love to hear anything from EA or CG about this issue.  Since we all agree this is about better communications, maybe the Community Manager can help improve the situation...  What do you think @CG_SBCrumb ?

[JumLx38]

@Resmi9793if EA or CG reacts to this post, I'm more than happy to help.

I tried one to unify all craches/freezes in one thread, to prevent spam of the same problem (since this is a bug report forum) but it was consider spamming from my side (since I was reporting all freezes I was having, not productive from my side either)

So if you have a positive reply from developers, I would be happy to contribute. Still have about a freeze per day, one yesterday during my GAC that almost cost my victory. 

If they don't react to this, I'll continue in my corner, until I get bored and quit the game for good.

Good luck and really nice initiative from your side.

[Resmi9793]

@JumLx38 Thanks. I also got a warning for spamming, which felt strange given how easy it was to find the duplicates... Surely this unified thread is what support should be creating, right?

Anyway, I'll update the thread if I ever get a response. In the meantime, I'm trying to stick to the letter of the forum rules so that this thread can help everyone. Do please feel free to add your diags to this thread if you can get them.

[GladOS-013]

---

@QuimSWGoH wrote:
you are not understanding that the main problem of thiese freezes and crashes is the communication. I think is happening in enough devices to worth it an announcement in the main forum. 

---

I would like to see more communication. I also understand some of the reasons they may not want to increase certain types of communication. Also keep in mind that your opinion of what is "worth it" may not be shared by the devs. 

---

@QuimSWGoH wrote:
, also I don't care if this forum not support the emulators, the emulators are important for this game,

---

It's not that "this forum" doesn't support emulators - SWGOH doesn't support emulators. The devs will only attempt to work on fixes and improvements on actual supported devices. If they made an adjustment and all phone/tablet crashes stopped, but emulators crashed 100% if the time, the devs would find that acceptable. 

I hear what you're saying, and I understand the frustrations. My personal frustrations actually went down when I started to understand how CG deals with these issues, which is why I try to help others understand the process. 

[GladOS-013]

---

@Resmi9793 wrote:
@JumLx38 Thanks. I also got a warning for spamming, which felt strange given how easy it was to find the duplicates... Surely this unified thread is what support should be creating, right?

---

Disclaimer: I'm not a moderator. 

I believe the warning was for bumping up 20+ threads on this page. That ended up pushing all other bug Reports of the front page, which is not the desired behavior - other bugs also deserve attention. 

Chatting on this thread should be fine. Attaching crash logs here should be fine, because you're adding investigative information each time. 

Posting a reply that says "just crashed again" several times a day would be an example of the type of behavior that might result in further warnings - it would keep bumping the thread repeatedly while providing no meaningful content. 

Once a bug has been flagged by HighCommand or UltraSlide, additional posts are unnecessary. Ideally, a player wanting to make a similar report would search, find a previous report, and either add their report as a comment or click the "Me too" button. All three separate posts exist because those posters were too lazy to search - even if a similar report was already one of the top posts. 

[Resmi9793]

@GladOS-013 Yup. That was the reason. And they were very quick to respond to that.

Seems strange that I'm doing all the legwork here since then. If they would just tell us what else we could do to help, that would be a massive improvement on where we are right now.

[Resmi9793]

Got a different error today aftr the Mon Mothma update downloaded.  Another memory allocation failure...

07-24 11:21:48.931 23793 24086 E AndroidRuntime: FATAL EXCEPTION: pool-9-thread-1
07-24 11:21:48.931 23793 24086 E AndroidRuntime: Process: com.ea.game.starwarscapital_row, PID: 23793
07-24 11:21:48.931 23793 24086 E AndroidRuntime: java.lang.Error: FATAL EXCEPTION [pool-9-thread-1]
07-24 11:21:48.931 23793 24086 E AndroidRuntime: Unity version     : 2018.4.19f1
07-24 11:21:48.931 23793 24086 E AndroidRuntime: Device model      : samsung SM-T810
07-24 11:21:48.931 23793 24086 E AndroidRuntime: Device fingerprint: samsung/gts210wifixx/gts210wifi:7.0/NRD90M/T810XXU2DRH1:user/release-keys
07-24 11:21:48.931 23793 24086 E AndroidRuntime:
07-24 11:21:48.931 23793 24086 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Fatal Exception thrown on Scheduler.Worker thread.
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:62)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.schedulers.ExecutorScheduler$ExecutorSchedulerWorker.run(ExecutorScheduler.java:110)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at java.util.concurrent.FutureTask.run(FutureTask.java:237)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:272)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at java.lang.Thread.run(Thread.java:762)
07-24 11:21:48.931 23793 24086 E AndroidRuntime: Caused by: android.database.CursorWindowAllocationException: Cursor window allocation of 2048 kb failed.
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at android.database.CursorWindow.<init>(CursorWindow.java:108)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at android.database.AbstractWindowedCursor.clearOrCreateWindow(AbstractWindowedCursor.java:198)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at android.database.sqlite.SQLiteCursor.clearOrCreateWindow(SQLiteCursor.java:300)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:138)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:132)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at android.content.ContentResolver.query(ContentResolver.java:555)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at android.content.ContentResolver.query(ContentResolver.java:478)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.upsight.android.internal.persistence.OnSubscribeFetchByType.call(OnSubscribeFetchByType.java:49)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.upsight.android.internal.persistence.OnSubscribeFetchByType.call(OnSubscribeFetchByType.java:19)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable$2.call(Observable.java:233)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable$2.call(Observable.java:225)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable$2.call(Observable.java:233)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable$2.call(Observable.java:225)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable$2.call(Observable.java:233)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable$2.call(Observable.java:225)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable$2.call(Observable.java:233)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable$2.call(Observable.java:225)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable$2.call(Observable.java:233)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable$2.call(Observable.java:225)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable$2.call(Observable.java:233)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable$2.call(Observable.java:225)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable.subscribe(Observable.java:8834)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.Observable.subscribe(Observable.java:8801)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.observables.BlockingObservable.blockForSingle(BlockingObservable.java:433)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.observables.BlockingObservable.first(BlockingObservable.java:160)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.upsight.android.analytics.internal.dispatcher.schema.LocationBlockProvider.fetchLatestLocation(LocationBlockProvider.java:119)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.upsight.android.analytics.internal.dispatcher.schema.LocationBlockProvider.get(LocationBlockProvider.java:91)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.upsight.android.analytics.internal.dispatcher.schema.Schema.getValueFor(Schema.java:133)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.upsight.android.analytics.internal.dispatcher.delivery.UpsightRequest$DefaultTypeAdapter.write(UpsightRequest.java:123)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.upsight.android.analytics.internal.dispatcher.delivery.UpsightRequest$DefaultTypeAdapter.write(UpsightRequest.java:108)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.google.gson.TypeAdapter$1.write(TypeAdapter.java:191)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.google.gson.Gson.toJson(Gson.java:661)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.google.gson.Gson.toJson(Gson.java:640)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.google.gson.Gson.toJson(Gson.java:595)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.google.gson.Gson.toJson(Gson.java:575)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.upsight.android.analytics.internal.dispatcher.delivery.UpsightEndpoint.send(UpsightEndpoint.java:189)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.upsight.android.analytics.internal.dispatcher.delivery.BatchSender$BatchSendTask.run(BatchSender.java:315)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at com.upsight.android.analytics.internal.dispatcher.delivery.BatchSender$1.call(BatchSender.java:220)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)
07-24 11:21:48.931 23793 24086 E AndroidRuntime:        ... 7 more