Integrated crashlogging tool
By Helge Gjølme. Wednesday, 18. March 2009, 12:46:31
Hi everybody!
I'm Helge, and I have been working at Opera Software for over three years. In the last year I have been handling many of the incoming crash bugs from our users.
I'm happy to inform you that we are finally getting an integrated crashlogger in Opera. This has already been implemented in the latest Windows builds of Opera 10, and it will soon be available for Mac and Linux. We put a lot of effort into stability, and this is an important step in the right direction to make Opera even more stable than it is. A crash is one of the worst things you can experience while browsing, and we are working very hard to fix crashes as we know that a stable browser is vital for our users.
For the moment on Windows, all crashlogs are saved in the Temp directory. This is just a temporary solution, while we get the automatic crashlog uploading to work. Before we can release the crashlog uploader we need to make sure that our backend for handling these crashlogs is working properly, and for that we need your help to test.
If you get a crash, please upload the crashlog to our new crashlog submitter.
Please enter as much information about what you were doing at the time of the crash in the Comments field. If for example Opera crashed while loading a page write something like:
Similar useful comments could be that: Opera crashed on exit, while closing a tab, while reading an e-mail etc.
If you get a crash that you can reproduce, please report the bug as a normal bug report here.
With this new automatic crashlogging tool we will hopefully get many more crashlogs than we did earlier, from all of our users, not just the users running inspectr. This requires a stable backend which can handle the load of the incoming crashlogs.
Note that if you experience freezes with Opera, please see our knowledge base article.
Do not upload freeze logs via the new crashlog submission form, but report a normal bug report here and send the freezelog to the bug's e-mail address.
I'm Helge, and I have been working at Opera Software for over three years. In the last year I have been handling many of the incoming crash bugs from our users.
I'm happy to inform you that we are finally getting an integrated crashlogger in Opera. This has already been implemented in the latest Windows builds of Opera 10, and it will soon be available for Mac and Linux. We put a lot of effort into stability, and this is an important step in the right direction to make Opera even more stable than it is. A crash is one of the worst things you can experience while browsing, and we are working very hard to fix crashes as we know that a stable browser is vital for our users.
For the moment on Windows, all crashlogs are saved in the Temp directory. This is just a temporary solution, while we get the automatic crashlog uploading to work. Before we can release the crashlog uploader we need to make sure that our backend for handling these crashlogs is working properly, and for that we need your help to test.
If you get a crash, please upload the crashlog to our new crashlog submitter.
Please enter as much information about what you were doing at the time of the crash in the Comments field. If for example Opera crashed while loading a page write something like:
Crash URL: http://www.example.com
Comments: Opera crashed while loading the page.
Similar useful comments could be that: Opera crashed on exit, while closing a tab, while reading an e-mail etc.
If you get a crash that you can reproduce, please report the bug as a normal bug report here.
With this new automatic crashlogging tool we will hopefully get many more crashlogs than we did earlier, from all of our users, not just the users running inspectr. This requires a stable backend which can handle the load of the incoming crashlogs.
Note that if you experience freezes with Opera, please see our knowledge base article.
Do not upload freeze logs via the new crashlog submission form, but report a normal bug report here and send the freezelog to the bug's e-mail address.
WIDGETIZE
1 2 Next »
eini # 18. March 2009, 13:01
Matthias # 18. March 2009, 13:19
Maybe a lot of people who are in a hurry forget about past crashes. Let's hope you guys get everything working very fast to improve Opera even more!
Dieu Anh Le Vu # 18. March 2009, 13:23
So, my question is, is that implemented in Opera 10 Turbo only ?
Helge Gjølme # 18. March 2009, 13:29
Dieu Anh Le Vu # 18. March 2009, 13:31
Kostia Romanov # 18. March 2009, 13:32
Ok, I`ll send you some of my crashreports :-)
skye11 # 18. March 2009, 14:02
hope this allows you guys to fix more bugs much faster
how about including a bug status report feature/database too?
and will this make 'Inspectr' crash logger obsolete?
Michael # 18. March 2009, 14:05
Now... conzentrate on Opera 10.0 to get it at least into beta state before Fx 3.5 is released! :-D
Tamil # 18. March 2009, 14:15
Charles Schloss # 18. March 2009, 14:25
Quantic # 18. March 2009, 14:25
z@h3k # 18. March 2009, 14:56
Zotlan # 18. March 2009, 15:12
Helge Gjølme # 18. March 2009, 16:58
Zoltan: Soon
Zotlan # 18. March 2009, 17:01
Originally posted by helgeag:
Good! i have a crash that needs logging.
Kyle Baker # 18. March 2009, 18:13
Annoynimous # 18. March 2009, 18:44
Phred # 18. March 2009, 20:05
lamarca # 18. March 2009, 21:06
we have to disable the inspector iixxii to get the integrated crashloging working, right?
Phred # 18. March 2009, 21:15
Originally posted by lamarca:
No, they work in conjunction with each other... sort of. If you disable the external inspectr, you can't make crash dumps when opera freezes.David Shamloo Ekblad # 18. March 2009, 21:23
I can't remember the last time I got a crash but it is nice to know that it will be easier to report them (now and in the future).
Charles Schloss # 18. March 2009, 21:29
Zotlan # 18. March 2009, 21:41
rriiicchh # 18. March 2009, 22:00
Originally posted by Chas4:
Hah, kind of funny.
I have been submitting crash reports through Smart Crash Reports addon in OSX for quite some time now and it is pretty seemless so it is nice to see this feature coming natively.
Do you want the crashlog logs in .zip?
Helge Gjølme # 18. March 2009, 22:17
Chas4: Yes, currently inspectr is not available for Mac, and the backend will only handle inspectr logs. Report Mac crashes in the normal way for now.
rriiicchh: You can send in crashlog in .zip format.
Charles Schloss # 19. March 2009, 00:13
Wade # 19. March 2009, 13:40
Zotlan # 19. March 2009, 13:44
olli # 19. March 2009, 13:52
Nonox # 19. March 2009, 14:01
Aux # 19. March 2009, 15:58
Phred # 23. March 2009, 12:44
Zotlan # 23. March 2009, 12:52
olli # 24. March 2009, 21:55
Kamalesh # 25. March 2009, 03:12
Kyle Baker # 25. March 2009, 07:54
@olli
That is a legit question. He is trying to help.
Zotlan # 25. March 2009, 08:54
Originally posted by olli:
heh, now where's that shamefaced smiley when you need it.
I guess i should have reread the post before i posted.
Haavard # 25. March 2009, 15:23
Safari, Chrome and Firefox have been optimized for those specific benchmarks. Some future version of Opera will have a new JS engine which will give similarly good results even on those artificial benchmarks.
Markus Teen # 26. March 2009, 16:18
David Gould # 26. March 2009, 16:26
Since I often have 40+ tabs open at a time, it's an incredible PITA to find the offending one (or two).
It would be great to have a tool which can isolate the offending site.
skye11 # 26. March 2009, 21:55
Originally posted by davegould:
+1
a crash logging feature should also allow Opera to detect & identify sites/tabs that are hanging and provide a way to stop & release them to free up the browser
a crash-preventative feature would be the ideal - to log & recognize offending sites or code, and prevent them from crashing Opera in the first place
yanjchan # 27. March 2009, 03:10
hobe # 27. March 2009, 17:38
Reza Fathzadeh # 27. March 2009, 22:48
Maxim # 28. March 2009, 17:38
Opera 10.0 build 1355
Jim # 29. March 2009, 02:52
Kyle Baker # 29. March 2009, 03:03
Originally posted by toyotabedzrock:
@fearphage was trying to get it included (I lost the link he posted a while back), but had no success. I think it had something to do with the fact that they didn't use Opera themselves, but I could be making that up. Maybe he can tell you why it wasn't included.
I would have been interested in seeing the results as well. It would also ahve been cool if they had to focus on each browser individually for a given amount of time so that each browser receives the same amount of attention towards trying to exploit it.
Phred # 29. March 2009, 09:12
Originally posted by kyleabaker:
Here's the link (in the comments).phantomderoper # 29. March 2009, 10:42
my personal feeling is that Opera is not taking care about such failure reports, I claimed a couple of times that the netbank solution from Danske netbank doesn't work under Opera, Ubuntu 810 and compiz 0.7.8, but there wasn't any interest from Opera to fix such failures, how should I recommend Opera to other users if many of the main function doesn't work at all?
Sorry, but for me its clear you should place more focus on this failure reports, and at least take the daily user more serios.
Phred # 29. March 2009, 15:41
Originally posted by phantomderoper:
To some extent, opera is interested in fixing most failures (we call them bugs). Did you file a bug report or just post comments in this blog? (A bug report is the correct answer)