BodyMakeマガシン vol.3
★┃夏┃に┃向┃け┃て┃★美人宣言☆ −− -- ＊ 夏はすぐそこ・・・あなたの身体、大丈夫？ ＊ -- この夏ノースリーブやキャミソールを着たいけどチョッと...そんな貴方に必見!! さぁ、涙を拭いて♪ 夏本番まであと少しですっ！ Ｄｒ．Ｂ１０で、 メリハリパーフェクトに、 大・変・身しちゃいましょっ♪(^▽^*) 「発掘!あるある大辞典」でも取り上げられた 「コエンザイムQ10」「α-リポ酸」「L-カルニチン」 この三つが貴方の体を大┃改┃造┃♪┃ ━┛━┛━┛━┛ 。・*☆。。・*☆。。・*☆。。・*☆。。・ ↓↓↓ ↓↓↓ ↓↓↓ 定価\12,600(税込)のところを、何と！ 今回は、ネット先行販売記念につき！！ キャンペーンコード※『2006』と入力頂ければ キャンペーン価格 [\9,870](税込)で 大奉仕しちゃいまーす！ このお値段は今だけ！ 詳┃し┃い┃資┃料┃請┃求┃は┃こ┃ち┃ら┃ ━┛━┛━┛━┛━┛━┛━┛━┛━┛━┛━┛ ↓↓↓ ↓↓↓ [EMAIL PROTECTED] 貴方のお悩みきっと解消します!! ＿＿＿ あなたにイイ事づくし。第三世代サプリ★ Ｄｒ．Ｂ１０ ★ ￣￣￣ 極┃上┃成┃分┃だ┃け┃を┃贅┃沢┃に┃厳┃選┃。┃ ━┛━┛━┛━┛━┛━┛━┛━┛━┛━┛━┛━┛━┛ ギ┃ュ┃ッ┃と┃詰┃め┃込┃ん┃だ┃自┃信┃作┃ ━┛━┛━┛━┛━┛━┛━┛━┛━┛━┛━┛━┛ 主成分： 核酸DNA・RNA、サラシア、コエンザイムQ10、α-リポ酸、L-カルニチン、 亜鉛酵母、 黒大豆エキス、クエン酸、オオバコ、シソエキス、葉酸、 ビフィズス菌、ナイアシ ン、パントテン酸Ca、ビール酵母、ビタミンB1、 ビタミンB2、ビタミンB6、ビタミン B12、ビタミンC、ビタミンE ■ この夏こそ…と思いつつ、諦めムードのアナタ必見♪ ■ (;_;)/ ＜ ずん胴は、もういや！！ (^Ｏ^)ノ ＜ ハヤりのビキニを着こなした〜い！ (>_<)/ ＜ 迫力のドラム缶体型をどうにかしてーっ！ ☆ まずはご連絡ください ☆ 詳┃し┃い┃資┃料┃請┃求┃は┃こ┃ち┃ら┃ ━┛━┛━┛━┛━┛━┛━┛━┛━┛━┛━┛ ↓↓↓ ↓↓↓ [EMAIL PROTECTED] 貴方のお悩みきっと解消します!! ●不要な方はこちらへ ↓↓↓ ↓↓↓ [EMAIL PROTECTED] -- 送信元：BodyMakeマガシン編集部 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kded memory leak
On 6/21/05, Zack Cerza <[EMAIL PROTECTED]> wrote: > On 2005 June 20 Monday 18:29, Ricardo Galli wrote: > > top is not the right tool to measure memory consumption. OTH the xfree > > memoryu consuption issue has been clarified several times. One is the top > > misleading figures, the others is that it counts the graphic card memory. > Er, I know that - but it's still ridiculous, no? It's not. In easy terms: You count your swap space as "memory" as well, it's simply mapped into the addressable space of your system. It's similar for the graphic card's memory. > What I don't know (and you didn't say) is what the right tool is. You could simply subtract the size of your card's memory from the value you get with top or ps. For more detailed information on memory usage: # cat /proc/`pidof X`/status | grep ^Vm Björn
Re: kded memory leak
On Monday 20 June 2005 07:31 pm, Zack Cerza wrote: > On 2005 June 20 Monday 18:29, Ricardo Galli wrote: > > On Tuesday, 21 de June de 2005 00:21, Zack Cerza shaped the electrons to > > > > shout: > > > Yep. From top, sorting by "%MEM": > > > > > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ > > > COMMAND > > > 9379 zack 15 0 2202m 409m 8640 S 0.0 40.4 9:31.38 kded > > > 9070 root 6 -10 100m 64m 2300 S 1.2 6.4 12:53.23 > > > XFree86 > > > [snip] > > > > > > I've got 1024MB of RAM, so it looks like kded is using over 400MB. The > > > next greediest process is XFree86, using about 60MB. Not cool. :) > > > > top is not the right tool to measure memory consumption. OTH the xfree > > memoryu consuption issue has been clarified several times. One is the top > > misleading figures, the others is that it counts the graphic card memory. > > Er, I know that - but it's still ridiculous, no? > > What I don't know (and you didn't say) is what the right tool is. > FWIW, I was using `ps axu | grep kded'. But it seems to give the same number as top, so... I don't know. Anyone?
Re: kded memory leak
On 2005 June 20 Monday 18:29, Ricardo Galli wrote: > On Tuesday, 21 de June de 2005 00:21, Zack Cerza shaped the electrons to > > shout: > > Yep. From top, sorting by "%MEM": > > > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ > > COMMAND > > 9379 zack 15 0 2202m 409m 8640 S 0.0 40.4 9:31.38 kded > > 9070 root 6 -10 100m 64m 2300 S 1.2 6.4 12:53.23 > > XFree86 > > [snip] > > > > I've got 1024MB of RAM, so it looks like kded is using over 400MB. The > > next greediest process is XFree86, using about 60MB. Not cool. :) > > top is not the right tool to measure memory consumption. OTH the xfree > memoryu consuption issue has been clarified several times. One is the top > misleading figures, the others is that it counts the graphic card memory. Er, I know that - but it's still ridiculous, no? What I don't know (and you didn't say) is what the right tool is. Zack
Re: kded memory leak
* Zack Cerza [Mon, 20 Jun 2005 18:21:31 -0400]: > > Anyone else see this? > Yep. From top, sorting by "%MEM": I can't confirm (session running for two days, will keep an eye during the week): PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 5219 adeodato 16 0 74744 14m 10m S 0.0 2.8 1:10.90 kded -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 The problem I have with making an intelligent statement is that some people then think that it's not an isolated occurrance. -- Simon Travaglia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
knode subject bug
Hi, here's an annoying bug in KNode: http://bugs.kde.org/show_bug.cgi?id=107032 I'd like to know if the patch is going to be applied in the next upload of KDE 3.4.1 ? Thanks in advance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kded memory leak
On Tuesday, 21 de June de 2005 00:21, Zack Cerza shaped the electrons to shout: > Yep. From top, sorting by "%MEM": > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ > COMMAND > 9379 zack 15 0 2202m 409m 8640 S 0.0 40.4 9:31.38 kded > 9070 root 6 -10 100m 64m 2300 S 1.2 6.4 12:53.23 XFree86 > [snip] > > I've got 1024MB of RAM, so it looks like kded is using over 400MB. The > next greediest process is XFree86, using about 60MB. Not cool. :) top is not the right tool to measure memory consumption. OTH the xfree memoryu consuption issue has been clarified several times. One is the top misleading figures, the others is that it counts the graphic card memory. -- ricardo galli GPG id C8114D34 http://mnm.uib.es/gallir/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kded memory leak
On 2005 June 20 Monday 16:49, Ian Eure wrote: > The 3.4.0 and 3.4.1 packages on alioth seem to have a pretty substantial > memory leak in kded. Over the course of a week or so of uptime, kded grew > to eat up over 500mb of memory, and bogged the system down severely. I > closed /all/ open apps, and the size didn't decrease substantially. > > Right now, kded is eating 241mb of ram, and I've only been logged in since > yesterday. > > Anyone else see this? Yep. From top, sorting by "%MEM": PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 9379 zack 15 0 2202m 409m 8640 S 0.0 40.4 9:31.38 kded 9070 root 6 -10 100m 64m 2300 S 1.2 6.4 12:53.23 XFree86 [snip] I've got 1024MB of RAM, so it looks like kded is using over 400MB. The next greediest process is XFree86, using about 60MB. Not cool. :) Zack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kded memory leak
Ian Eure wrote: > The 3.4.0 and 3.4.1 packages on alioth seem to have a pretty substantial > memory leak in kded. Over the course of a week or so of uptime, kded grew > to eat up over 500mb of memory, and bogged the system down severely. I > closed /all/ open apps, and the size didn't decrease substantially. > > Right now, kded is eating 241mb of ram, and I've only been logged in since > yesterday. > > Anyone else see this? > > Yes, i've killed kded thinking it might collapse kde and then i have to rebbot, but no! the system started to run nicely and i haven't notice any errors so far -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kded memory leak
The 3.4.0 and 3.4.1 packages on alioth seem to have a pretty substantial memory leak in kded. Over the course of a week or so of uptime, kded grew to eat up over 500mb of memory, and bogged the system down severely. I closed /all/ open apps, and the size didn't decrease substantially. Right now, kded is eating 241mb of ram, and I've only been logged in since yesterday. Anyone else see this? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
KDE 3.4.0-PRE bug report
I understand we're supposed to send bug reports on the KDE 3.4.0-pre packages to this list, so here's one. Most things have been working fine since switching to the new packages. However, Konqueror crashes far more often now, but only on File Browser mode. I've not noticed much of a pattern yet, but did grab the backtrace from the last crash. I've pasted it below. Anyone have any ideas about the cause, or how to keep it from crashing? -- (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1230268384 (LWP 8055)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #3 0xb763be48 in QGList::first () from /usr/lib/libqt-mt.so.3 #4 0xb7c1d08b in KDirListerCache::slotUpdateResult () from /usr/lib/libkio.so.4 #5 0xb7c21db4 in KDirListerCache::qt_invoke () from /usr/lib/libkio.so.4 #6 0xb738371c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #7 0xb7b71e3a in KIO::Job::result () from /usr/lib/libkio.so.4 #8 0xb7b5a13c in KIO::Job::emitResult () from /usr/lib/libkio.so.4 #9 0xb7b5b65c in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.4 #10 0xb7b646ae in KIO::ListJob::slotFinished () from /usr/lib/libkio.so.4 #11 0xb7b75293 in KIO::ListJob::qt_invoke () from /usr/lib/libkio.so.4 #12 0xb738371c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #13 0xb7383544 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #14 0xb7b5034e in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.4 #15 0xb7b4eeb1 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4 #16 0xb7b4e3b9 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4 #17 0xb7b4bdeb in KIO::Slave::gotInput () from /usr/lib/libkio.so.4 #18 0xb7b4db08 in KIO::Slave::qt_invoke () from /usr/lib/libkio.so.4 #19 0xb738371c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #20 0xb738387d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #21 0xb76c3452 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3 #22 0xb739ff00 in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3 #23 0xb7326e1f in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #24 0xb732641e in QApplication::notify () from /usr/lib/libqt-mt.so.3 #25 0xb78a5ac5 in KApplication::notify () from /usr/lib/libkdecore.so.4 #26 0xb731681a in QEventLoop::activat
Re: Cookies Stop Working?!
* Jarkko Suontausta [Sun, 19 Jun 2005 00:44:38 +0300]: Hi Jarkko! > Hopefully this will be fixed soon... Is there any place, then, (e.g., an upstream bug report) where the problem is explained, and solutions being discussed? Thanks, -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 You cannot achieve the impossible without attempting the absurd. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
BEST CANNON. PROMOTIONAL VIDEO CAMERA ONLY $ 49.99
CANNON BEST PRICES PROMOTIONAL PROMOTIONAL PROMOTIONAL PROMOTIONAL PROMOTIONAL Click: http://bessel.allhyper.com/redir.html for order Best Video Sell Video Camera Cannon MVX35i + MVX35i kit at best prices of market Digital Video Camera Cannon MVX35i at Only: $ 49.99 Best Video Sell REAL PRICES IS $ 229.99 BEST BUY. BUY NEW AT ONLY $ 49.99 IN STOCK PROMOTIONAL PROMOTIONAL PROMOTIONAL PROMOTIONAL PROMOTIONAL Click: http://bessel.allhyper.com/redir.html for order SPAM IS VERY BAD. NEVER SEND IT -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
