Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

crash on network type changes 2.9.111b #1272

Closed
Michael23456 opened this issue Jun 11, 2017 · 4 comments
Closed

crash on network type changes 2.9.111b #1272

Michael23456 opened this issue Jun 11, 2017 · 4 comments
Assignees
Labels
Bug
Milestone

Comments

@Michael23456
Copy link

@Michael23456 Michael23456 commented Jun 11, 2017

since 2.9b, adguard seems to crash on network type changes like wifi to 4g and back again

state.txt
debug (35).txt
CustomerID: 1350712

@ameshkov ameshkov added the Bug label Jun 11, 2017
@ameshkov ameshkov self-assigned this Jun 11, 2017
@ameshkov ameshkov added this to the 2.9 R2 milestone Jun 11, 2017
@ameshkov

This comment has been minimized.

Copy link
Member

@ameshkov ameshkov commented Jun 14, 2017

10:39:32.060 [pool-2-thread-264] ERROR com.adguard.android.commons.c - Thread: Thread[pool-2-thread-264,5,main]; Uncaught exception:

java.lang.NullPointerException: Attempt to invoke virtual method 'void com.adguard.android.filtering.filter.i.a()' on a null object reference
	at com.adguard.android.filtering.vpn.FilteringVpnService.d(Unknown Source) ~[na:0.0]
	at com.adguard.android.filtering.vpn.FilteringVpnService$2.run(Unknown Source) ~[na:0.0]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) ~[na:0.0]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) ~[na:0.0]
	at java.lang.Thread.run(Thread.java:761) ~[na:0.0]
@ameshkov

This comment has been minimized.

Copy link
Member

@ameshkov ameshkov commented Jun 14, 2017

@Michael23456 please ask user to collect "record everything"-level log

@Michael23456

This comment has been minimized.

Copy link
Author

@Michael23456 Michael23456 commented Jun 16, 2017

we are waiting for an answer from the customer

@ameshkov

This comment has been minimized.

Copy link
Member

@ameshkov ameshkov commented Jun 19, 2017

Added a simple check to prevent it. If it ever happens with a newer build, please reopen this issue.

@ameshkov ameshkov closed this Jun 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.