"White Screen of Death"

Tim Sweetman ti at lemonia.org
Tue Jan 22 16:14:12 GMT 2008

That sort of behaviour can be caused by use of eval within DESTROY,  
which then erases $@ before it gets checked. You might want to check  
for DESTROYs doing anything clever, or calling anything which has an  


On 22 Jan 2008, at 13:00, Chisel Wright <chisel at herlpacker.co.uk> wrote:

> I'm sorry for posting something on-topic. I'm also sorry for being a  
> bit
> vague ... I'm just posting to see if I'm alone in this particular
> suffering.
> I'm working on $project at $orkplace - a project that was in common  
> and
> general use long before I arrived.
> It's Apache1, mod_perl, TT and straight DBI.
> As part of a recent extension to $project I added DBIx::Class to the
> mix. (I don't know if this is related)
> In the "good old days", if I messed up I'd get an error or warning in
> the logs .. the usual plethora of messages I'd expect to see from my  
> own
> typos.
> At some point, at _roughly_ the same time in introduced DBIC to the  
> mix
> things changed. All of a sudden, a large proportion of errors started
> producing what I lovingly refer to as the "White Screen Of Death":
> nothing but a white page in the browser, and no messages in the logs.
> Wrapping stuff in an eval{...} at high-levels doesn't seem to catch
> anything. I've had to start adding warns and lower-level eval{...}
> blocks just to find out where the error is occurring.
> The total lack of output makes it hard to know where to start looking.
> My gut-feeling is that DBIC is catching errors itself, and somehow
> preventing them from propagating them back up ...

More information about the london.pm mailing list