Bug#283612: 1.3.18-1.1 is a CPU hog

2005-02-04 Thread Alban browaeys
Le mercredi 02 février 2005 à 23:52 -0500, Michel Dänzer a écrit :

  you can do this by saving them as a directory in the
  bookmarks,then importing galeon bookmarks in the other browser.
  In the new browser right clicking on the bookmark folder and
  choosing open in a new tab (konqueror) or open in new tabs
  mozilla will do hte trick.
 
 Thanks, but that'll result in all tabs being in a single window, right?
 That's not exactly the same thing as my former Galeon session, but I
 don't know if the difference is relevant...

yes and no. THe first part , saving the tabs as a bookmarks folder work
per window, so the issue is mostly fixed by saving each window tabs to a
new bookmark folder. Then in the second part opening a new window before
opening folder as tabs.
If there is a lot of tabs per windows that s ok, if you have 80 windows
with only a few tabs for each one, the problem remain.

Alban

Did i said Daniel ? sorry about that i need new binoculars :)




Bug#283612: 1.3.18-1.1 is a CPU hog

2005-02-02 Thread browaeys . alban
Hi Daniel

I may do that if someone provides me with a way to do it that doesn't
 involve opening all the 150 tabs manually. I already mentioned that the
 bug is probably somewhere outside of Galeon, feel free to reassign the
 bug if you know where.

you can do this by saving them as a directory in the
bookmarks,then importing galeon bookmarks in the other browser.
In the new browser right clicking on the bookmark folder and
choosing open in a new tab (konqueror) or open in new tabs
mozilla will do hte trick.

Maybe there was a swapping problem also. The new galeon use less
memory, that could fix it.

Regards
Alban



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#283612: 1.3.18-1.1 is a CPU hog

2005-02-02 Thread Loïc Minier
Hi,

[EMAIL PROTECTED] - Wed, Feb 02, 2005:

 Hi Daniel

 Excuse me, but who is the Daniel you are writing to?

   Bye,

-- 
Loïc Minier [EMAIL PROTECTED]
Neutral President: I have no strong feelings one way or the other.



Bug#283612: 1.3.18-1.1 is a CPU hog

2005-02-02 Thread Michel Dänzer
On Wed, 2005-02-02 at 14:01 +0100, [EMAIL PROTECTED] wrote:
 Hi Daniel

???

 I may do that if someone provides me with a way to do it that doesn't
  involve opening all the 150 tabs manually. I already mentioned that the
  bug is probably somewhere outside of Galeon, feel free to reassign the
  bug if you know where.
 
 you can do this by saving them as a directory in the
 bookmarks,then importing galeon bookmarks in the other browser.
 In the new browser right clicking on the bookmark folder and
 choosing open in a new tab (konqueror) or open in new tabs
 mozilla will do hte trick.

Thanks, but that'll result in all tabs being in a single window, right?
That's not exactly the same thing as my former Galeon session, but I
don't know if the difference is relevant...

 Maybe there was a swapping problem also. The new galeon use less
 memory, that could fix it.

Well, my GNOME session was pretty deep into swap most of the time, but
that was never a problem before.


-- 
Earthling Michel Dnzer  | Debian (powerpc), X and DRI developer
Libre software enthusiast|   http://svcs.affero.net/rm.php?r=daenzer



Bug#283612: 1.3.18-1.1 is a CPU hog

2005-01-16 Thread Michel Dänzer
On Fri, 2005-01-14 at 11:02 +0100, Loc Minier wrote: 
 
 Michel Dnzer [EMAIL PROTECTED] - Tue, Dec 14, 2004:
 
  Actually, I'm seeing the same symptoms with 1.3.17-2 as well now, so I
  suspect it's actually caused by some library...
 
  Or the contents of the tabs changed?

They did, but I doubt they changed significantly between the last time I
suspended and resumed the machine before and the first time I ran
1.3.18-1.1 . I think it's much more likely that some library was
upgraded between the last time I started the version of Galeon before
1.3.18-1.1 and the first time I started that version, a time span of
days or even weeks.


  It'd be nice if you could give a precise example of what Galeon does
  wrong, for example compared with another browser: Mozilla only uses 1%
  CPU where Galeon uses 20% on http://foobar.example.com;.  I understand
  it is not a regression in Galeon itself, but might be a regression in
  some library, did you find out which library that is?  

Unfortunately not.

 Or at least in which time frame this happened?

The first time I noticed it was with 1.3.18-1.1. I am fully aware that
this is very little information (the only other information I can think
of is the aptitude logs if you guys think they'd be useful?) and don't
expect any more help than is appropriate considering that.

In the meantime, I've converted my session to bookmarks instead of
restoring it and am rebuilding it on demand.


-- 
Earthling Michel Dnzer  | Debian (powerpc), X and DRI developer
Libre software enthusiast|   http://svcs.affero.net/rm.php?r=daenzer