aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Pages: 1 [2]

Author Topic: CPU & Memory problem on !?  (Read 7235 times)

Xaignar

  • Admin and Code Junky
  • Hero Member
  • *****
  • Karma: 19
  • Offline Offline
  • Posts: 1103
Re: CPU & Memory problem on !?
« Reply #15 on: March 18, 2005, 06:59:46 AM »
Quote
Originally posted by skolnick
I think the problem is not the -lnsl, since I could compile the amule executable without it, and it would run fine (March 6) . -lnsl is only needed if I need to compile amuleweb. Also, I don't use amuleweb for now, and the memory leakage is there...

Regards.
Well, that commit was added the 7th, after the last currently known working date, which is partly why I considered it. Also, as I said above, the other reason why I considered it suspect was that the commit has caused _both_ amule itself and amuleweb to be linked against that library though it is only amuleweb that actually required it.
Logged

skolnick

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 24
  • Offline Offline
  • Posts: 1188
  • CentOS 6 User
Re: CPU & Memory problem on !?
« Reply #16 on: March 18, 2005, 07:16:05 AM »
OK, so if this is true, and the problem is the linking against -lnsl, then compiling CVS from March 6 *should* also produce memory leakage on amule right? well, I'm trying that right now, and keep you informed in this thread.

Regards.
Logged

Xaignar

  • Admin and Code Junky
  • Hero Member
  • *****
  • Karma: 19
  • Offline Offline
  • Posts: 1103
Re: CPU & Memory problem on !?
« Reply #17 on: March 18, 2005, 07:37:12 AM »
Sorry? Why would a change added the 7th have any effect on a snapshot from the 6th? You'd have to grab the one from the 7th which would contain those changes.
Logged

skolnick

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 24
  • Offline Offline
  • Posts: 1188
  • CentOS 6 User
Re: CPU & Memory problem on !?
« Reply #18 on: March 18, 2005, 05:07:07 PM »
no,no,no, the commit made the 7th was only to link automatically against -lnsl, before that, -lnsl was still necessary, but had to be done manually, (LDFLAGS=-lnsl) that's why I think it might also trigger the failure, but I might be wrong.

Regards.
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: CPU & Memory problem on !?
« Reply #19 on: March 18, 2005, 06:32:22 PM »
It's not related to nls.
Logged

Vollstrecker

  • Administrator
  • Hero Member
  • *****
  • Karma: 67
  • Offline Offline
  • Posts: 1549
  • Unofficial Debian Packager
    • http://vollstreckernet.de
Re: CPU & Memory problem on !?
« Reply #20 on: March 18, 2005, 10:08:24 PM »
Xaignar: If it was added at 7th, it is in the snapshot of 8th. The snaps are taken somewhere beetween 5 and 8 in the morning.
Logged
Homefucking is killing prostitution

Xaignar

  • Admin and Code Junky
  • Hero Member
  • *****
  • Karma: 19
  • Offline Offline
  • Posts: 1103
Re: CPU & Memory problem on !?
« Reply #21 on: March 18, 2005, 10:24:49 PM »
I know.
I did however manually verify it before I specified that date in my previous post. The CVS commit mail was sent to me at 05:34 in the morning, apparently before the snapshot was made.
Logged

skolnick

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 24
  • Offline Offline
  • Posts: 1188
  • CentOS 6 User
Re: CPU & Memory problem on !?
« Reply #22 on: March 19, 2005, 10:15:01 PM »
OK, so far, so good. I'm testing amule from March 10 (known to fill the memory) just with onlinesig disabled, and is working perfectly. Using wx2.5.4, GTK1 no unicode. Seems the problem is onlinesig...

Regards.
Logged
Pages: 1 [2]
« previous next »