line.
If I can do anything more to help debug this tell me.
Jim Gallacher wrote:
dharana wrote:
I think there is a problem with the autocleaning function in
FileSession. I'm using Mod_Python 3.2.2b in a live server and I today
I noticed this:
/tmp/mp_sess # df -h /tmp
Filesystem
23857 104911 19% /tmp
So I think FileSession isn't doing its work. Any ideas?
--
dharana
configure: error: This version of mod_python only works with Python
major version 2. The one you have seems to be .
---
--
dharana
test
output, and suggestions, if any).
Thank you,
Jim Gallacher
>
--
dharana
uot; release was 3.1.3 in Feb 2004, which makes
it 18
months (if my math is correct)
Grisha
--
dharana
ome bug it disappears _after_ sending the email.Sorry
for bothering you.
Jim Gallacher wrote:
dharana wrote:
dharana wrote:
Uh oh, no it doesn't goes away. Check this (custom handler):
-- controller.py ---
import os
from time import time
from mod_python import apache
dharana wrote:
Uh oh, no it doesn't goes away. Check this (custom handler):
-- controller.py ---
import os
from time import time
from mod_python import apache
from mod_python import Session
def handler(req):
start_time = time()
req.sess = Session.FileSessio
over 70Mb. Is this right? (I'm asking for both the load time and
memory usage)
dharana wrote:
Please, ignore my previous email. The massive leak was being caused by
FileSession. I was using an earlier snapshot and after upgrading to:
http://svn.apache.org/snapshots/mod_python/mo
78.221.360.53 |
-++---+---+---+---+---++
If anyone want to plays with my benchmark scripts let me know and I'll
post them.
Regards,
Jim
--
dharana
me a lot of time and it's tuned for my
needs. I won't look into using Vampire for that reason.
(Just my newbie opinion on that matter)
--
dharana
thon
related and until I have a testcase for it from the beginning.
Thank you all for your help.
--
dharana
te the object's attributes. Althought it's
weird (imo) that this could cause a segfault, it's weirder because the User
object (class User(Storable)) _works_ correctly if I store it in session and it
does exactly the same thing.
I hope to have made it as clear as possible. This is
results. I will post the weird results I
got one minute later in my next email.
(I've also commented Nicholas email below)
Nicolas Lehuen wrote:
Hi dharana, I have a two parts answer :
1) One thing I'm really sure is that there is no way for the pickle
module to handle the request
rg/jira/browse/MODPYTHON-45
I can't see wether this has anything to do with the problem at hand but just in
case.
Jim Gallacher wrote:
Hi dharana,
I've been away for a few days, but should have some time to mess around
with this today.
--
dharana
or the spam. My head starts spinning really fast when I see
segfaults.
dharana wrote:
This is driving me crazy. I'm finding it hard to make a simple testcase.
I use a custom handler and somewhere in the code I do this:
-- [snip] --
trieve more info from the
segfault? I don't like segfaults :( they don't tell why they don't like you.
dharana wrote:
More information about the segfault. It always happens after a certain
ammount of time. I believe it maybe this:
- session starts correctly
- I navigate throught
d out more info or I find an easy to reproduce testcase.
Jim Gallacher wrote:
dharana wrote:
I don't know if it's related but I'm having some troubles with the
current FileSession implementation. It causes a segfault when I do this:
- login creating a session and go to any pa
ified by some very low level issues that they have to solve by
themselves. Other web frameworks are a little more helpful. Do we
really want developers to loose time thinking about whether the number
of times they already instantiated a Session object ?
Regards,
Nicolas
--
dharana
[
http://issues.apache.org/jira/browse/MODPYTHON-45?page=comments#action_65715 ]
dharana commented on MODPYTHON-45:
--
mod_python/Session.py from (mod_python_20050518163650.tar.gz) has a typo at
line +364:
if timeout:
self
19 matches
Mail list logo
