public void onModuleLoad() {
Timer t = new Timer() {
public void run() {
greetingService.greetServer(
new
AsyncCallback() {
public void
onF
On 8 mar, 01:05, "dolcra...@gmail.com" wrote:
> Does it still happen if you define the callback and assign it to a
> final variable and use it that way?
And how about scheduling the timer from the onSuccess/onFailure?
Is the leak also experienced when scheduling every, say, 10 secs?
It could
Does it still happen if you define the callback and assign it to a
final variable and use it that way?
On Mar 7, 5:00 pm, "winhqwebm...@gmail.com"
wrote:
> Hello,
>
> I am developing a small application that requires an AsyncCallback
> call every second. The following implementation generates a f
I also forgot to mention that I am using Chrome for testing.
On Mar 7, 5:00 pm, "winhqwebm...@gmail.com"
wrote:
> Hello,
>
> I am developing a small application that requires an AsyncCallback
> call every second. The following implementation generates a fairly
> considerable memory leak:
>
> publ
Hello,
I am developing a small application that requires an AsyncCallback
call every second. The following implementation generates a fairly
considerable memory leak:
public void onModuleLoad() {
Timer t = new Timer() {
public void run() {
g
