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

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?

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...

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