http://redmine.emweb.be/http://redmine.emweb.be/favicon.ico?16934085252010-11-09T13:12:01ZRedmineWt - Bug #590: Destructor of WApplication is not called anymorehttp://redmine.emweb.be/issues/590?journal_id=14942010-11-09T13:12:01ZKoen Deforchekoen@emweb.be
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>Hey Christophe,</p>
<p>Catching the browser/tab/window close does not work on all browsers and in all circumstances. Are you sure the very same setup worked before? We do not see any regression.</p>
<p>Regards,<br><br>
koen</p>
Wt - Bug #590: Destructor of WApplication is not called anymorehttp://redmine.emweb.be/issues/590?journal_id=15062010-11-16T10:06:54ZChristophe Delépinechristophe.delepine@thalesgroup.com
<ul></ul><p>Hi Koen,</p>
<p>YES i am 100% sure the very same setup worked with wt dated 24/09/2010. I have just retried again and the destructor is always called with previous wt but never with wt 3.1.6<br><br>
I am running a 64-bit non multithreaded build of wt with a httpd connector<br><br>
This is with Firefox 3.6.10</p>
<p>Regards<br><br>
Christophe</p>
Wt - Bug #590: Destructor of WApplication is not called anymorehttp://redmine.emweb.be/issues/590?journal_id=15362010-11-24T13:15:31ZChristophe Delépinechristophe.delepine@thalesgroup.com
<ul></ul><p>FYI, i have just tried with the latest git and the problem is still there</p>
Wt - Bug #590: Destructor of WApplication is not called anymorehttp://redmine.emweb.be/issues/590?journal_id=15372010-11-24T14:55:07ZChristophe Delépinechristophe.delepine@thalesgroup.com
<ul></ul><p>Also note that when i kill the browser window, the following message is printed twice in the console :</p>
<p>Asio error: 4121: An established connection was aborted by the software in your host machine</p>
Wt - Bug #590: Destructor of WApplication is not called anymorehttp://redmine.emweb.be/issues/590?journal_id=15492010-11-25T12:54:41ZChristophe Delépinechristophe.delepine@thalesgroup.com
<ul></ul><p>Koen,</p>
<p>Do you want me to set a breakpoint somewhere in debug to see what is going on when i kill the firefox window ?</p>
Wt - Bug #590: Destructor of WApplication is not called anymorehttp://redmine.emweb.be/issues/590?journal_id=15762010-11-27T21:47:46ZKoen Deforchekoen@emweb.be
<ul></ul><p>Hey Christophe,</p>
<p>I went back though older version of Wt to see if I ever got this working using Firefox but could not manage so far. Can you trigger the correct behaviour using Firefox with standard examples of Wt? If so, are you using a special wt_config.xml and how does your setup look like: same computer for client/server, and what browser and OS ?</p>
<p>I believe that the unreliability of detecting a browser closing is a race condition between the browser closing and the asynchronous request to notify the server being sent, and there is alot that could influence that I would suspect.</p>
<p>Regards,<br><br>
koen</p>
Wt - Bug #590: Destructor of WApplication is not called anymorehttp://redmine.emweb.be/issues/590?journal_id=15782010-11-29T09:21:04ZChristophe Delépinechristophe.delepine@thalesgroup.com
<ul><li><strong>File</strong> <a href="/attachments/239">wt_config.xml</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/239/wt_config.xml">wt_config.xml</a> added</li></ul><p>Hi Koen,</p>
<p>I tried using the wt_config.xml that is delivered in wt-3.1.6 and now the destructor is called !<br><br>
The one i was using was provided by an older version of wt.</p>
<p>Can you have a look at the file and tell me what setting caused the problem ?</p>
<p>Thanks<br><br>
Christophe</p>
Wt - Bug #590: Destructor of WApplication is not called anymorehttp://redmine.emweb.be/issues/590?journal_id=15792010-11-29T09:26:58ZChristophe Delépinechristophe.delepine@thalesgroup.com
<ul></ul><p>P.S. i am using a httpd connector</p>
Wt - Bug #590: Destructor of WApplication is not called anymorehttp://redmine.emweb.be/issues/590?journal_id=15842010-12-01T16:03:10ZChristophe Delépinechristophe.delepine@thalesgroup.com
<ul></ul><p>Koen,</p>
<p>I have found the setting that cause the problem :</p>
<p>false</p>
<p>if set to true, then the destructor is called.</p>
<p>Is that normal ?<br><br>
Note that i do not reload the session. I just kill the browser tab.</p>
<p>Regards<br><br>
Christophe</p>
Wt - Bug #590: Destructor of WApplication is not called anymorehttp://redmine.emweb.be/issues/590?journal_id=15852010-12-01T22:07:21ZKoen Deforchekoen@emweb.be
<ul></ul><p>Hey Christophe,</p>
<p>I was starting to think there was other magic involved since I could not reproduce your problem.</p>
<p>Because a browser refresh cannot be distinguished (easily) from a window closing, we ignored the unload event when we support session refreshes. Perhaps this could be fixed by adding a heuristic where a Wt-unload is ignored right after the session is refreshed --- and still that depends on an ordering of events in the browser that I have not found to be documented (i.e. that the request for the new page precedes the unload event of the previous page). So that will require a bit of experimentation to determine whether it is actually possible.</p>
<p>Regards,<br><br>
koen</p>
Wt - Bug #590: Destructor of WApplication is not called anymorehttp://redmine.emweb.be/issues/590?journal_id=15862010-12-02T08:17:07ZChristophe Delépinechristophe.delepine@thalesgroup.com
<ul></ul><p>ok thanks for the explanation<br><br>
i can live with this setting set to true.<br><br>
You can close the bug</p>
<p>regards<br><br>
christophe</p>
Wt - Bug #590: Destructor of WApplication is not called anymorehttp://redmine.emweb.be/issues/590?journal_id=15872010-12-02T13:19:12ZKoen Deforchekoen@emweb.be
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul>