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

Transmission dies out after awhile #10

Open
beyondthetech opened this issue Sep 30, 2010 · 6 comments
Open

Transmission dies out after awhile #10

beyondthetech opened this issue Sep 30, 2010 · 6 comments

Comments

@beyondthetech
Copy link

The current build of iProxy initially works well, but seems to die off after a while, and I no longer can surf on Safari. I've tested this in various modes, with both HTTP and SOCKS turned on, only one of them on, and either multitasking in the background, or left running in the foreground.

I manually have to end it and restart the app in order to resume the ability to surf.

This is being tested on a non-jailbroken iPhone 4 running iOS 4.1 and a MacBook running Snow Leopard 10.6.4.

Thanks for all your help in advance!

@beyondthetech
Copy link
Author

FYI, I am able to revert back to 1.0.1 until the issue with 2.0 is resolved. 1.0.1 does not have this issue, as I am able to surf and download for hours without incident.

@jeromelebel
Copy link
Contributor

do you have any clue how many pages do you have to watch before the application die off? does it crash (quit by itself), or does it stop working?

@beyondthetech
Copy link
Author

It does not quit, it just sits there. I don't know how many pages, it seems random. Sometimes when I'm downloading a file in Safari, the progress bar just stops and the time remaining increases indefinitely.

@jeromelebel
Copy link
Contributor

is it about minutes or about hours to reproduce this bug?

@beyondthetech
Copy link
Author

It never lasts more than several minutes at a time before I have to manually shut it down and restart.

@thetrebor
Copy link

i've noticed this as well. A few times i got a browser message about the proxy server having trouble allocating the object (503 error)
I'm guessing there is a memory leak.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants