494215 - Hitting Commit button after adding bug comment results in blank page

Status: RESOLVED WORKSFORME

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[Jim Hood]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)
Build Identifier: BUGZILLA-3_3_4 and BUGZILLA-3_4-BRANCH

I can add a new bug successfully.  Upon adding a comment to an existing but and pressing the Commit button, I get a blank browser page.  The url in the address bar when the blank page is presented is:

http://bugzilla.mydomain.com/process_bug.cgi

This happens on any existing bug in any status.  The comment does make it into the database since a subsequent viewing of the bug entry displays the comment just entered.

In an attempt to work around the issue, I have tried changing "After changing a bug" setting in Administration > Default Preferences.  Changing of this parameter has no effect on the outcome, regardless of its value.

Reproducible: Always

Steps to Reproduce:
1. From homepage, click on red search button (or search link) 
2. Find a bug (status=All, Product=All, Words field is empty)
3. Click Search button
4. Click on any bug in the search results
5. Type text into the "Additional Comments" field
6. Click Commit button below Additional Comments field
Actual Results:  
Blank page appears... process_bug.cgi in address bar

Expected Results:  
Browser returned to updated bug page per setting of "Show the updated bug" for the "After changing a bug" parameter in Default Preferences.

Comment 1

[Teemu Mannermaa (:wicked)]

I couldn't reproduce this on landfill's bugzilla-3.4-branch install and this is a problem that's hard to go unnoticed. Could you provide more information to help track this problem down? Do you use mod_perl? Do you use UTF8 (non-ASCII chars) in comments? Are you logged in or logged out? Are you really running Bugzilla on Vista (or was that platform just autodetected)? Any local customizations that could have broken your install?

Comment 2

[Jim Hood]

Hi Teemu - I agree.. this is a very strange one.

I have corrected the platform to Linux (from the Vista default).  I am using straight ASCII characters in the comments and am logged in at the time.  No local customizations either.

What Perl modules and database columns participate in posting a bug comment? I could report back on the module versions and/or DB data for what you feel makes sense to check.

Comment 3

[Jim Hood]

Forgot to answer your mod_perl question: no, I am not using this.

Comment 4

[Frédéric Buclin]

I'm pretty sure this is a problem with your MTA, in which case this is a support question.

Comment 5

[Jim Hood]

Frederic - how do you come to this conclusion?  What do you see in this situation that points to an MTA problem?

Comment 6

[Frédéric Buclin]

Go to editparams.cgi, section 'Email', set 'mail_delivery_method' to 'none', and check again. If the page is displayed correctly, then you know it's a problem with your MTA, which is not a bug in Bugzilla. Only reopen this bug if this parameter change doesn't help.

Comment 7

[Max Kanat-Alexander]

Really, what we're saying here is that we can't reproduce your problem, so it's a local issues, not a bug. If you want assistance, the best thing to do is to use one of the support resources listed at http://www.bugzilla.org/support/

Comment 8

[Jim Hood]

I have been testing the same thing.  The problem still persists when the mail_delivery_method parameter is set to 'None'

Even if MTA configuration were the cause, the software crashing to a blank page is an very ungraceful way for an app to fail... regardless of the reason.

Comment 9

[Jim Hood]

Max - the software should be robust enough to generate an exception page to report back on what part of the code failed so that the admin has something to work with to remedy the situation.  A blank page is quite useless.

Comment 10

[Dennis Benn]

I've got the same problem. I've made an update from 3.2.3 to 3.3.4 and if I change a bug it result in a blank site. The modifications are done but the screen is white. If I test it on landfill there is no blank screen. I don't think it's only a local issue. There must be a difference between our installation and the landfill one.

Comment 11

[Dennis Benn]

Ok I've got some new informations by testing. In my case it seems to be a Problem with Firefox. If I try it with IE 7 it works, but with firefox it don't.

Comment 12

[Bradley Baetz (:bbaetz)]

Diagnosing this with Jim on IRC has pointed to this being a template toolkit bug.

A workaround is to edit Bugzilla/Template.pm, and add:

$Template::Config::STASH = 'Template::Stash';

to the start of |sub _init| (before the PARSER line). This disables the compiled template toolkit stash and uses the pure-perl one instead.

Still trying to work out what the actual problem is