Re: 100% CPU Utilization, looping with gettimeofday calls

Dnia 2009-08-24, pon o godzinie 14:42 +0200, Ruari Ødegaard pisze:
> On Thu, 20 Aug 2009 14:01:43 +0200, Witold Baryluk  
> <[email protected]> wrote:
> 
> > Dnia 2009-08-19, śro o godzinie 13:55 +0200, Ruari Ødegaard pisze:
> >> On Wed, 19 Aug 2009 12:34:29 +0200, Witold Baryluk
> >> <[email protected]> wrote:
> >>
> >> Hi Witold,
> >>
> >> > Hi guys.
> >> >
> >> > I was reporting this bug many times. But still probably
> >> > Opera developers are ignoring this.
> >> >
> >> > Opera is running tight loop with millions of gettimeofday calls.
> >> >
> >> > http://smp.if.uj.edu.pl/~baryluk/opera10_few_seconds_of_strace.txt.gz
> >> >
> >> > This is present sine 9.6x series, and is present in all snapshots,
> >> > including Beta3 and 4546.
> >>
> >> Below is some information from Arjan van Leeuwen,
> >>
> >> "Unfortunately, this information is not useful to developers. Although  
> >> the
> >> gettimeofday() calls are the only thing you can see with strace (since
> >> there are no other system calls), they are not what is causing the 100%
> >> CPU usage. And since no one at Opera has ever reproduced this bug, it's
> >> pretty difficult to see what's going on on your system.
> >>
> >> "What might help is to create a crash log for Opera once this is  
> >> happening.
> >> To do this, wait until you are in this situation, and then send Opera a
> >> SIGABRT signal using kill. This should trigger the crash report dialog.
> >> Make sure to describe the situation you are in within the crash report,
> >> tell
> >> us it's a freeze and not a crash, and provide your email address so that
> >> we can contact you for further details. You can send several reports  
> >> like
> >> this - they are likely to be different, and one of them might provide  
> >> the
> >> hint that is needed."
> >>
> >
> > Hi, i prepared simple script, which:
> > 1. restores ~/.opera (rsync with another 700MB directory)
> > 2. starts opera with no tabs
> > 3. measure CPU utilisation of opera
> > 4. sends ABRT, wait, and send it again
> > 5. copy crash report
> > 6. kill all operas
> > 7. goto 1
> >
> >
> >
> > Now i have about 200 crash reports, and about 100 of them
> > have this problem with high CPU utilisation. (in top it is 85%,
> > in ps it is about 50-60^).
> >
> > I have posted another post but it is awaiting moderation (it have 26KB)
> >
> > Where to send this crash report files crash*.txt ?
> > I can provide them to trusted Opera developer using my HTTP server.
> > It is 90MB uncompressed now.
> 
> Considering your method I doubt there is that much variation. Send me the  
> first 5 and I'll have a look to see.
> 

I send you this data about month ago, any progress. AFAIK nobody from
Opera even downloaded this data from my server.

Of course newest versions of opera is still having this problem.

Regards,
Witek

-- 
Witold Baryluk

--
Opera-Linux: https://list.opera.com/mailman/listinfo/opera-linux
More lists: https://list.opera.com/mailman/listinfo/
Unsubscribe: mailto:[email protected]?subject=unsubscribe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAkq2bzIACgkQ7ZLFFOttZ4LdcQCgsKfEVWMybKzIPkeNoNmXvrjg
TGUAoMJwjIBZoLqRxwimR66DK+2Z8PSA
=qriS
-----END PGP SIGNATURE-----