Project

General

Profile

Actions

Bug #480

closed

Wt session crashed when bringing up a message box via exec() in Wt 3.1.4

Added by Thian-Peng Ter over 13 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
High
Assignee:
Target version:
-
Start date:
08/20/2010
Due date:
% Done:

0%

Estimated time:

Description

The Wt session crashed when enabling server push (e.g., enableUpdates(true)) or invoking a message box via exec(). This appears to be a 3.1.4 bug, and the problem does not occur in 3.1.2 and 3.1.3. I attach the same example as in #465.

Here are my environment settings:

  • Dedicated process
  • num-threads = 20 in connector-fcgi
  • Embedded Linux
  • Google Chrome

After invoking DialogExample, the Wt session crashed and then restarted a new session.

[notice] "Caught SIGCHLD: pid=4002, stat=11"
[notice] "Deleting session: QOyvEebY06Ipt6YO"
[error] "Error writing to application"
[notice] "Spawned dedicated process for fH41e13Tm34M5pXQ: pid=4023"
[notice] "Wt: initializing session process"
...

If I disable server push, upon clicking the "One liner" button, a loading indicator showed up. The loading indicator stayed until the "Wt internal error" message showed up.


Files

DialogExample.zip (1.98 KB) DialogExample.zip Thian-Peng Ter, 08/20/2010 12:26 AM
configure.log (6.39 KB) configure.log Thian-Peng Ter, 08/20/2010 06:02 PM
Actions #1

Updated by Koen Deforche over 13 years ago

  • Status changed from New to Feedback

Hey Thiang-Pang,

I cannot reproduce this. Are you sure Wt was built with threading support enabled ? Do you get any other error before 'Caught SIGCHLD' ?

Regards,

koen

Actions #2

Updated by Thian-Peng Ter over 13 years ago

I checked that multi-threading was enabled during configuration. Please see the attached log file. Unfortunately, there is no additional error message, except the usual error message:

FastCGI: incomplete headers ...
Actions #3

Updated by Thian-Peng Ter over 13 years ago

I also tried running the example on Ubuntu 9.10. The Wt session did not crash when running on the built-in http server. However, it crashed when running on FastCGI.

May I know that were you running on FastCGI when trying to reproduce the error?

Thank you.

Actions #4

Updated by Koen Deforche over 13 years ago

  • Status changed from Feedback to Resolved
  • Assignee set to Koen Deforche

Hey Thian-Peng,

There is indeed a regression with the FastCGI connector, WDialog::exec() and server push, in Wt 3.1.4. The latest git fixes the problem.

Regards,

koen

Actions #5

Updated by Thian-Peng Ter over 13 years ago

Thank you for your timely response. Would you please kindly point out the file(s) that I need to patch? Thanks.

Actions #6

Updated by Koen Deforche over 13 years ago

Hey Thian-Peng,

Because we worked also on implementing WSocketNotifier consistently, the patch will not cleanly apply to Wt 3.1.4. I recommend grabbing the latest git version.

Regards,

koen

Actions #7

Updated by Thian-Peng Ter over 13 years ago

I carefully looked into the changes and then manually patched each of those files. The patches appeared to work, and the Wt session no longer crashes!

Thanks again for your timely response. I look forward to the 3.1.5 release.

Actions #8

Updated by Koen Deforche over 13 years ago

  • Status changed from Resolved to Closed

Fixed in Wt 3.1.5

Actions

Also available in: Atom PDF