Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Frequent crashes on Snow Leopard, shell output included

13 views
Skip to first unread message

Martin

unread,
May 30, 2010, 10:09:02 AM5/30/10
to
I know this issue has been discussed here before, but noone seems to
have developed any idea why Opera (10.53, 10.54 snapshot) crash on
some systems (jus as mine). The crashes happen every half hour or so,
and they even happen if you do not use the browser at all (err, maybe
something does happen, like page reloads are triggered via Javascript
etc.). I have disabled all plugins, only Javascript support is
active.

This extreme instability makes Opera virtually unusable. It gets
particularly annoying if you are editing text in a Wiki or stuff like
that and in midst of it the browser crashes. Since this is a highly
critical problem, could anyone out there @opera comment on it? Since
on my system this happens just every time I run opera, maybe I could
volunteer in tracking down the problem. I am a software developer and
I know hot to use a debugger :)

When I run Opera from the command line I get this output after the
crash:

Opera(330,0xa0afc4e0) malloc: *** mmap(size=16777216) failed (error
code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Opera(330,0xa0afc4e0) malloc: *** mmap(size=16777216) failed (error
code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Opera(330,0xa0afc4e0) malloc: *** mmap(size=16777216) failed (error
code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Opera(330,0xa0afc4e0) malloc: *** mmap(size=16777216) failed (error
code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Opera(330,0xa0afc4e0) malloc: *** mmap(size=16777216) failed (error
code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Opera(330,0xa0afc4e0) malloc: *** mmap(size=16777216) failed (error
code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Opera(330,0xa0afc4e0) malloc: *** mmap(size=16777216) failed (error
code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Opera(330,0xa0afc4e0) malloc: *** mmap(size=16777216) failed (error
code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Killed

Nosferatu

unread,
Jun 6, 2010, 3:58:26 PM6/6/10
to
Hello Martin,

I suggest you go back to version 10.10 as this works fine, Unfortunately
there does not appear to be anywhere on the Opera website to report
catastrophic problems such as this with the software, It seems that Opera
suffers the Microsoft disease of relying upon the end user to sort the
problem out for themselves. It's a shame because when Opera is a stable
browser it is hard to find anything so good.


--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Rijk van Geijtenbeek

unread,
Jun 7, 2010, 10:10:33 AM6/7/10
to
Op Sun, 06 Jun 2010 21:58:26 +0200 schreef Nosferatu
<gdmit...@ntlword.com>:

> Hello Martin,
>
> I suggest you go back to version 10.10 as this works fine, Unfortunately
> there does not appear to be anywhere on the Opera website to report
> catastrophic problems such as this with the software, It seems that
> Opera suffers the Microsoft disease of relying upon the end user to sort
> the problem out for themselves. It's a shame because when Opera is a
> stable browser it is hard to find anything so good.

There's a bug report wizard if you do a little searching on the website.
But for crashers, since 10.0 we have a dedicated crash logger tool that
should pop-up right after Opera crashes, making it possible to send very
useful (for us) crashlogs to our servers. The developers are always
working on fixing the most often reported crashers.


--
Rijk van Geijtenbeek
Opera Software ASA, Documentation & QA
Tweak: http://my.opera.com/Rijk/blog/

"The most common way to get usability wrong is to listen to what users
say rather than actually watching what they do." - J.Nielsen

Nosferatu

unread,
Jul 15, 2010, 8:01:59 PM7/15/10
to
Thanks Rijk,

In my opinion Opera blundered here. These fundamental problems should be
found and fixed in testing before releasing the software. It's hard enough
beating the MS IE, Mozilla, Safari stranglehold without releasing duff
software releases. We need a stable version of Opera released with a note
stating they've fixed the crash problems. Otherwise I'm sticking to my
reliable 10.10 until it becomes unusable in a year or two.

Regards,
G


--

0 new messages