Comment 11 for bug 296903

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

dust - from the upstream bug report:

"The valgrind log doesn't seem to have resulted from the same programme run that
produced the crash, so offers no info on it. The crash itself is in gecko code.

The valgrind log however does contains some mem leaks and invalid reads in yelp
and rarian, which should be fixed separately of course."

Would you mind providing another valgrind log from a run where the crash occurs?

Thanks