Game crash on raid in Edge

6 Replies
Craniopath
25 August, 2016, 4:41 AM UTC

The game crashes and reloads slowly, frequently crashing again when reloading. Once reloaded the game is painfully slow at best.



This version of the game is the most unstable by far and needs to be updated soon...

UTC +0:00
Alyona Kolomiitseva
Community Manager
25 August, 2016, 9:54 AM UTC

Please follow this instruction when it crashes:


1. Access Chrome -> More Tools -> Developer Tools - http://screencast.com/t/dXnNlwFTV8y6


2. Access Network tab http://screencast.com/t/rRKZ9T9bsG


3. Try to access the game


4. Do the right click on any line and tick Save as HAR with content http://screencast.com/t/gxsrje20g


5. Input the following command in cmd: tracert plarium.hs.llnwd.net Then make a screenshot of it.


6. Send this information to our Support Team: http://support.plarium.com/Tickets/Submit/.


They will help you to understand the reason of your crashes and will help you to fix them.

Plarium Community Manager. Please note that I will be unable to respond to your private messages, review your tickets, or check your account information. All technical issues should be directed to our Support Team at plrm.me/Support_Plarium
UTC +2:00
Craniopath
25 August, 2016, 6:41 PM UTC

I will take a look at that but this is not related to Chrome; at least not in this report:




1. Browser of interest and for report: Microsoft Edge on Windows 10


2. This issue happens ONLY when performing raids and can be reproduced by many others; especially of you use a fast raid technique where the raids hit within 40 to 35 seconds of each other AND you attempt to apply the single or double van trick (no difference as the issue appears related to an issue with the animation at the target sector(s)).


Do you still request what seems like an irrelevant tracert or do you propose a more comprehensive investigation related to a potential memory leak in this versions of the game?

UTC +0:00
Craniopath
25 August, 2016, 6:51 PM UTC

Steps to reproduce issue:


1.launch raids on at least 5 bot sectors within about 30 to 40 seconds of each other (one after the other in quick succession)


2. Go to the sector where the first raid will hit within about 60 to 45 seconds of landing to give yourself time to perform a single van push


3. at 30 seconds before the raid is to hit, perform a push (res type irrelevant)


4. IF no crash move to the next raid in line and repeat until the game crashes


My experience is that the game should spontaneously crash on the second or third raid but YMMV. This to me indicates a memory leak issue and not a connection issue between client and server or visa-versa...

UTC +0:00
Alyona Kolomiitseva
Community Manager
26 August, 2016, 9:48 AM UTC
Please report your issue to our Support Team. They will test it and forward to our developers.
Plarium Community Manager. Please note that I will be unable to respond to your private messages, review your tickets, or check your account information. All technical issues should be directed to our Support Team at plrm.me/Support_Plarium
UTC +2:00
Coldcut
15 September, 2016, 1:56 AM UTC

i have 2 OS's  xp and win7 each having chrome and Firefox 

so ,2 different  machines having this same exact issue of crashing seconds before a raid lands just as the op sez.



you got bug.

UTC +0:00
fakeasnever
Moderator
15 September, 2016, 8:54 PM UTC

@ColdCut (15 September, 2016, 1:56 AM UTC):
I would recommend following Alyona Kolomiitseva's instructions on how to report this issue.

If they do indeed have a bug, more information about it can help them solve it faster.

If Internet Explorer still asks to be your default browser, then you can do anything :D
UTC +0:00
1660871 users registered; 33441 topic; 252446 posts; our newest member:eloralva