-
Notifications
You must be signed in to change notification settings - Fork 353
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
Memory leak #216
Comments
Your comment was wrong. Read the code again. It does retrieve it from a
static map based on context, so what you said wouldn't happen.
Also, I don't have to tolerate any abusive language. Your comment was
irritating and condescending.
And now you are just being an asshole. Good day to you sir.
…On Mon, 23 Oct 2017 at 13:27 Predrag Čokulov ***@***.***> wrote:
Instead of facing that your library is poorly designed you deleted my
commend that actually helps people (shows how to workaround above issue),
Great job.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#216 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAgnI0DeUl859Bi9U25mz-uqOgPXks_7ks5svIYxgaJpZM4Ph4YZ>
.
|
I don't know if English is a second language to you both, but the following
phrases do not contain "abusive" language.
"*No offense* to the creator of the library but *in my opinion* this is
poor api design
*Please* correct me if I'm wrong"
On Mon, Oct 23, 2017 at 8:37 AM, Nacho Lopez <notifications@github.com>
wrote:
… Your comment was wrong. Read the code again. It does retrieve it from a
static map based on context, so what you said wouldn't happen.
Also, I don't have to tolerate any abusive language. Your comment was
irritating and condescending.
And now you are just being an asshole. Good day to you sir.
On Mon, 23 Oct 2017 at 13:27 Predrag Čokulov ***@***.***>
wrote:
> Instead of facing that your library is poorly designed you deleted my
> commend that actually helps people (shows how to workaround above issue),
> Great job.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#216#
issuecomment-338642539>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-
auth/AAgnI0DeUl859Bi9U25mz-uqOgPXks_7ks5svIYxgaJpZM4Ph4YZ>
> .
>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#216 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAA6lyO54WHjrg4JM_OfAmsg9RqrpJdtks5svIiRgaJpZM4Ph4YZ>
.
--
Chris Scott
Transistor Software <http://www.transistorsoft.com>
|
It is not a nice thing to say to anyone, and even less in the context of an
OSS project. There are proper and more polite ways of addressing such
concerns. In my humble opinion, that person was wrong.
Thanks.
…On Mon, 23 Oct 2017 at 13:42 Chris Scott ***@***.***> wrote:
I don't know if English is a second language to you both, but the following
phrases do not contain "abusive" language.
"*No offense* to the creator of the library but *in my opinion* this is
poor api design
*Please* correct me if I'm wrong"
On Mon, Oct 23, 2017 at 8:37 AM, Nacho Lopez ***@***.***>
wrote:
> Your comment was wrong. Read the code again. It does retrieve it from a
> static map based on context, so what you said wouldn't happen.
>
> Also, I don't have to tolerate any abusive language. Your comment was
> irritating and condescending.
>
> And now you are just being an asshole. Good day to you sir.
>
> On Mon, 23 Oct 2017 at 13:27 Predrag Čokulov ***@***.***>
> wrote:
>
> > Instead of facing that your library is poorly designed you deleted my
> > commend that actually helps people (shows how to workaround above
issue),
> > Great job.
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <#216#
> issuecomment-338642539>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-
> auth/AAgnI0DeUl859Bi9U25mz-uqOgPXks_7ks5svIYxgaJpZM4Ph4YZ>
> > .
>
> >
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <
#216 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AAA6lyO54WHjrg4JM_OfAmsg9RqrpJdtks5svIiRgaJpZM4Ph4YZ
>
> .
>
--
Chris Scott
Transistor Software <http://www.transistorsoft.com>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#216 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAgnIyfXoLws_5s1RhrTwX_lJXnWU1Vyks5svIm3gaJpZM4Ph4YZ>
.
|
@mrmans0n why this issue closed? Is it solved? Thanks for the hard work btw! |
I do also have this problem. The code that produces it, is just this code in a FragmentDialog:
|
I have made a pull request that makes it possible for me to solve the problem #240 |
Samsung Galaxy S7 on Android 7.0
Using SmartLocation version 3.3.2
LeakCanary info:
Code:
The text was updated successfully, but these errors were encountered: