My OperaThe My Opera forums have been replaced with forums.opera.com. Please head over there to discuss Opera's products and features
See the new ForumsYou need to be logged in to post in the forums. If you do not have an account, please sign up first.
Suggestion to instrument pure virtual function calls
Hi, I am using Opera 12 (build 1065) rather extensively, both at home and at work, and dutifully send all crash reports.But more than any other crashes, I experience MSVC++ Runtime message box(es) with "R6025 - C++ error - Pure virtual function call" message and abort. It would be wise to instrument this exit point so I can send these crash reports as well. I don't know how exactly is this implemented in MSVC++ runtime, so I can't provide any further guidelines, but I would expect there to be a call to std::terminate.
Myself being user of GCC/MinGW I would be "overriding" the __cxxabiv1::__cxa_pure_virtual function :)
Originally posted by Tringi:
dutifully send all crash reports.
The latest snapshot - Opera 12 build 1076 has a lot of crash fixes, try it.
Windows 7 SP1 x86 edition and Windows XP Service Pack 3.
If you need any help from me with regards to Opera, please make a comment on any of my blog posts.
Support Opera wishes
If you need any help from me with regards to Opera, please make a comment on any of my blog posts.
Support Opera wishes
I wish I could.
If I could trace steps leading (with some probability) to these crashes I would have already filled a bug report.
These happens to me after half a day (maybe longer) of using the browser, thats why I am asking for a way to report them, so the developers could go through the stack traces and dumps to find out what is wrong.
Regarding tab stacks, I use them only occasionally, still waiting for that "wheel-click or ctrl+click opens tab in same stack" functionality.
If I could trace steps leading (with some probability) to these crashes I would have already filled a bug report.
These happens to me after half a day (maybe longer) of using the browser, thats why I am asking for a way to report them, so the developers could go through the stack traces and dumps to find out what is wrong.
Regarding tab stacks, I use them only occasionally, still waiting for that "wheel-click or ctrl+click opens tab in same stack" functionality.
I tried to reproduce your steps but no crash for me (1076) that way.
Anyway I can't really 100% tell if the crash happened in 1047 for me, but it is likely it did. I think it started with first build of Opera 12, but I don't remember the build number.
What might be important is, that often I see that error message multiple times, as if invoked recursively or, more likely, from different threads.
Anyway I can't really 100% tell if the crash happened in 1047 for me, but it is likely it did. I think it started with first build of Opera 12, but I don't remember the build number.
What might be important is, that often I see that error message multiple times, as if invoked recursively or, more likely, from different threads.
Maybe if you update Microsoft Visual C++ 2010 Redistributable Package (x86) ...
http://www.microsoft.com/download/en/details.aspx?id=5555
http://www.microsoft.com/download/en/details.aspx?id=5555
Using Windows 7 64Bit SP1 and of course Opera
(If nothing else stated the most current weekly) on a nice Dell Studio XPS 16!
(If nothing else stated the most current weekly) on a nice Dell Studio XPS 16!
I also often get "pure virtual function call" on 12.00.1328 on Win7 x64 and on couple of previous 12.00.x versions. There is no exact steps to reproduce, but it seems it sometimes happens few seconds after I close some tab when 30+ tabs are opened. And also this message very often appears after I close Opera, few seconds after Opera main window dissapears.
Forums » Opera for Windows/Mac/Linux » Beta testing (including snapshots and previews)