InterviewSolution
Saved Bookmarks
InterviewSolution
| 1. |
Solve : Firefox crashes after some interval? |
|
Answer» Hi, Download BlueScreenView:Does that really apply to a browser crash? As I understand the OP's situation, his browser crashed, not his OS, not his computer, so he does not actually get BSOD screens. Quote from: sagngh8 link=topic=113955.msg762792#msg762792 I am trying to take the screen shot of the browser using selenium Rc.Why not just use the Print Screen button on your keyboard? Holding the Alt key before pressing the Print Screen button captures only the active window, not the entire screen; that's useful when you want to capture a window that does not cover your entire display area. From one of the many many threads you've started all over the place about this: Quote It would probably be more helpful to go into Firefox and enter "about:crashes" in the address bar (without the quotes), and click on one or more of the most recent crashes logged, and copy that info over to this thread. That as well as trying Firefox with all addons disabled except for Selenium IDE. Quote from: soybean on December 20, 2010, 08:13:22 AM Does that really apply to a browser crash?We won't know until we see the report, will we? I'd like to be sure.Quote from: Allan on December 20, 2010, 09:11:40 AM We won't know until we see the report, will we? I'd like to be sure.Well, I'm not familiar with that diagnostic app but will a report even be generated if no actual BSOD occurs? Again, the issue here is a browser crash, not BSOD.BSODViewer is for viewing BSOD ERRORS. BSOD errors are from kernel MODE faults. the "program.exe has stopped working" errors are General Protection faults that occur in user mode. No dump information will be stored where BlueScreenViewer will look for it. Firefox stores dump information when it crashes (and uploads it to Mozilla, if "submit crash reports" is enabled) These are accessed by using about:crashes to view such information, and provide Firefox-specific information about the state of the program when it crashed, as well as what plugin/addons/extensions and so forth are installed. However, googling for their error message, firefox, as well as this "selenium" product, it is not an uncommon problem, even if we ignore the 6 or 7 other forums that this exact question has been copy-pasted to. Since the program in question acts as a firefox plugin, either the plugin itself is causing the problem or the plugin is conflicting with some other installed plugin. Thus my suggestion to try running with only the selenium plugin active. (Safe mode would fix the problem but only because they would no longer be using the add-on at all).You guys are right and I'm wrong. I took a quick look at the error message and thought it was a crash dump not an app error. My mistake and thanks for keeping the OP on track |
|