seen on linux embed from yesterday (2002-03-04-10-trunk) and today (2002-03-05-11-trunk) unfortunately I can't reproduce the crash by going to the site by hand. It only crashes on this page in the memory test script I run daily. I also cannot get gdb to work in the test environment. This is actually a blocker for me and this test. But the other embed smoketests pass. Also, I believe, and jrgm concurs, that this just might be the same as bug 128492. (crash in cookie code)
You mean bug 128942 probably.
yep, I did mean to say bug 128942. anyway, I can no longer reproduce the crash from that bug. I had my own test case (which, unfortunately was on a news site, and thus is out of date). So I tried the ask jeeves test case and wasn't able to reproduce that crash. However, and perhaps coincidentally, the memtest made it past the www.cnn.com page in the momory test, but crashes a few sites later. The test had been crashing at cnn everytime. Perhaps the cookiebug was that? and now it's crashing for some other reason? I was hoping that when the cookie bug went away that this would work. Now I don't know where to look. This is blocking memory testing I am supposed to be running daily. My guess is if I upgrade severity to blocker that it'll simply get dropped back as to not hold the tree hostage. So I'll leave it as is and ask nicely; Please fix this. :-)
seems asking nicely works. I don't know who what or why fixed this, but the memory test didn't crash today. marking wfm. will verify with mondays test run.
the test has been able to get past cnn.com no problem