Re: reproducible memory problem and crashes on cygwin: TRACEBACK INCLUDED

2006-07-13 Thread emacs user
here is a traceback of a crash under cygwin.  am happy to provide more 
information, but please note that I am a total ignorant and needs very 
specific instructions on what to do in gdb etc.  thanks for any feedback... 
EU



[EMAIL PROTECTED]:~ $ cd /usr/local/emacs/src/
[EMAIL PROTECTED]:/usr/local/emacs/src $ gdb emacs
GNU gdb 6.5.50.20060706-cvs (cygwin-special)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.

Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as i686-pc-cygwin...
DISPLAY = :0.0
TERM = dumb
Breakpoint 1 at 0x2009da26: file emacs.c, line 464.
Breakpoint 2 at 0x200b6cd9: file sysdep.c, line 1395.
(gdb) run
Starting program: /usr/local/emacs/src/emacs.exe -geometry 80x40+0+0
Loaded symbols for /cygdrive/c/WINDOWS/system32/ntdll.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/kernel32.dll
Loaded symbols for /usr/bin/cygncurses-8.dll
Loaded symbols for /usr/bin/cygwin1.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/advapi32.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/rpcrt4.dll
Loaded symbols for /usr/bin/cygjpeg-62.dll
Loaded symbols for /usr/bin/cygpng12.dll
Loaded symbols for /usr/bin/cygz.dll
Loaded symbols for /usr/bin/cygtiff-5.dll
Loaded symbols for /usr/bin/cygungif-4.dll
Loaded symbols for /usr/X11R6/bin/cygX11-6.dll
Loaded symbols for /usr/X11R6/bin/cygICE-6.dll
Loaded symbols for /usr/X11R6/bin/cygSM-6.dll
Loaded symbols for /usr/X11R6/bin/cygXaw3d-7.dll
Loaded symbols for /usr/X11R6/bin/cygXext-6.dll
Loaded symbols for /usr/X11R6/bin/cygXmu-6.dll
Loaded symbols for /usr/X11R6/bin/cygXt-6.dll
Loaded symbols for /usr/X11R6/bin/cygXpm-4.dll

Breakpoint 3 at 0x2007f3ac: file xterm.c, line 7822.
cont

Breakpoint 1, abort () at emacs.c:464
464   kill (getpid (), SIGABRT);
(gdb) Continuing.
  2703 [main] emacs 1136 _cygtls::handle_exceptions: Exception: 
STATUS_ACCESS_VIOLATION

warning: HEAP[emacs.exe]:
warning: HEAP: Free Heap block 264280 modified at 264284 after it was freed


Program received signal SIGTRAP, Trace/breakpoint trap.
0x7c901231 in ntdll!DbgUiConnectToDbg ()
  from /cygdrive/c/WINDOWS/system32/ntdll.dll
(gdb) where
#0  0x7c901231 in ntdll!DbgUiConnectToDbg ()
  from /cygdrive/c/WINDOWS/system32/ntdll.dll
#1  0x7c96c943 in ntdll!RtlpNtMakeTemporaryKey ()
  from /cygdrive/c/WINDOWS/system32/ntdll.dll
#2  0x00229210 in ?? ()
#3  0x7c949eb9 in ntdll!RtlInsertElementGenericTableAvl ()
  from /cygdrive/c/WINDOWS/system32/ntdll.dll
#4  0x00264280 in ?? ()
#5  0x021a in ?? ()
#6  0x0025 in ?? ()
#7  0x0001 in ?? ()
#8  0x202fc1f9 in bss_sbrk_buffer ()
#9  0x062c in ?? ()
#10 0x in ?? ()

Lisp Backtrace:
format (0x21757b53)
server-sentinel (0x21861e04)
kill-this-buffer-enabled-p (0x202ee801)
(gdb) backtrace
#0  0x7c901231 in ntdll!DbgUiConnectToDbg ()
  from /cygdrive/c/WINDOWS/system32/ntdll.dll
#1  0x7c96c943 in ntdll!RtlpNtMakeTemporaryKey ()
  from /cygdrive/c/WINDOWS/system32/ntdll.dll
#2  0x00229210 in ?? ()
#3  0x7c949eb9 in ntdll!RtlInsertElementGenericTableAvl ()
  from /cygdrive/c/WINDOWS/system32/ntdll.dll
#4  0x00264280 in ?? ()
#5  0x021a in ?? ()
#6  0x0025 in ?? ()
#7  0x0001 in ?? ()
#8  0x202fc1f9 in bss_sbrk_buffer ()
#9  0x062c in ?? ()
#10 0x in ?? ()

Lisp Backtrace:
format (0x21757b53)
server-sentinel (0x21861e04)
kill-this-buffer-enabled-p (0x202ee801)
(gdb) xbacktrace
format (0x21757b53)
server-sentinel (0x21861e04)
kill-this-buffer-enabled-p (0x202ee801)
(gdb)

_
On the road to retirement? Check out MSN Life Events for advice on how to 
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement




___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: reproducible memory problem and crashes on cygwin

2006-07-11 Thread emacs user

From: Nick Roberts [EMAIL PROTECTED]

  thanks   so I get nil in the echo area and the memory usage does 
not
  change at all when I try this.  I didnt try leaving emacs for 1/2 an 
hour.

  it normally crashes with a segmentation something much earlier.

Spontaneously?  If you post a backtrace as Eli suggested (as described with
M-x report-emacs-bug), someone might be able to understand the problem.


I did that a few times last year but no one was able to help.  I could try 
again.  but this memory thing seems to be easily reproducible.  Am I the 
only person in the universe running cvs emacs on cygwin?  no emacs cygwin 
maintainer currently around?


_
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/




___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: reproducible memory problem and crashes on cygwin

2006-07-11 Thread Eli Zaretskii
 From: emacs user [EMAIL PROTECTED]
 Bcc: 
 Date: Tue, 11 Jul 2006 12:37:19 -0400
 Cc: emacs-pretest-bug@gnu.org
 
 Am I the only person in the universe running cvs emacs on cygwin?

No.  But I don't use the Cygwin port.

 no emacs cygwin maintainer currently around?

Sorry, no.  There never was such a maintainer, AFAICR.


___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: reproducible memory problem and crashes on cygwin

2006-07-11 Thread Eli Zaretskii
 From: emacs user [EMAIL PROTECTED]
 Date: Tue, 11 Jul 2006 12:37:19 -0400
 Cc: emacs-pretest-bug@gnu.org
 
 Spontaneously?  If you post a backtrace as Eli suggested (as described with
 M-x report-emacs-bug), someone might be able to understand the problem.
 
 I did that a few times last year but no one was able to help.

That doesn't mean you should stop trying.  It could be a different
problem, or someone could be reading your report who previously
didn't.

 I could try again.

Please do.  Thanks.


___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: reproducible memory problem and crashes on cygwin

2006-07-10 Thread Eli Zaretskii
 From: emacs user [EMAIL PROTECTED]
 Bcc: 
 Date: Mon, 10 Jul 2006 01:05:40 -0400

Thank you for your report.

 this problem leads to consistent and reproducible crashes of emacs.

You didn't show any crashes.  Please do (with meaningful backtraces).

 using latest cvs gnu emacs (22.0.50) on latest cygwin.

Which version of Cygwin is that?  We had in the past reports about
various problems in specific versions; please try to search the
archives of this list and of emacs-devel, and see if your crashes
resemble some reported in the past.

 start with
 emacs -q --no-site-file
 edit a jpeg file
 kill buffer
 edit another jpeg file
 kill buffer again.
 
 every such jpeg file edited and exited leaves the memory used by emacs (as 
 seen in the list of processes of the windows task manager) increased.  

Please report the numbers: the memory usage figures reported by the
Task Manager before, during, and after the image buffer is killed.

 Memory does not decrease once buffer with image is killed.  when a text file 
 is edited and exited, the memory does return to its original size.

I don't think Emacs returns the memory to the OS immediately, but GC
should cause that.


___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: reproducible memory problem and crashes on cygwin

2006-07-10 Thread emacs user





From: Eli Zaretskii [EMAIL PROTECTED]

 From: emacs user [EMAIL PROTECTED]

Thank you for your report.

 this problem leads to consistent and reproducible crashes of emacs.

You didn't show any crashes.  Please do (with meaningful backtraces).


so emacs uses more and more memory, and eventually slows down my laptop so 
much that I either have to kill it (OK, not exactly a crash, I suppose), or 
that it somehow dies.  wouldnt this be sufficient information to the cygwin 
maintainer to work with?  even without the crash, this seems like a fairly 
significant bug...?



 using latest cvs gnu emacs (22.0.50) on latest cygwin.

Which version of Cygwin is that?  We had in the past reports about
various problems in specific versions; please try to search the
archives of this list and of emacs-devel, and see if your crashes
resemble some reported in the past.


the cygwin home page suggests that  Latest Cygwin DLL release version is 
1.5.20-1
is this what you were looking for?  how do I find the cygwin version number? 
 I am trying to be well intentioned but am certainly a total ignorant as a 
non fortran programmer


I did follow the links you suggested in a previous email, but couldnt 
understand if they are relevant or not to this specific problem, or the 
previous one I reported.



 start with
 emacs -q --no-site-file
 edit a jpeg file
 kill buffer
 edit another jpeg file
 kill buffer again.

 every such jpeg file edited and exited leaves the memory used by emacs 
(as

 seen in the list of processes of the windows task manager) increased.

Please report the numbers: the memory usage figures reported by the
Task Manager before, during, and after the image buffer is killed.


an example:

before editing the image: 33Mb
during: 39Mb
after killing the buffer: 39Mb
image file is 186263 bytes large (jpeg)

 Memory does not decrease once buffer with image is killed.  when a text 
file

 is edited and exited, the memory does return to its original size.

I don't think Emacs returns the memory to the OS immediately, but GC
should cause that.


I'll take your word for that, I hardly know what GC is...

_
Don’t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/




___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: reproducible memory problem and crashes on cygwin

2006-07-10 Thread Jason Rumney

emacs user wrote:

an example:

before editing the image: 33Mb
during: 39Mb
after killing the buffer: 39Mb
image file is 186263 bytes large (jpeg)


Emacs needs to decompress your jpeg image to display it, and rather than 
do that every time it gets displayed, it caches the decompressed image 
for image-cache-eviction-delay seconds after it was last displayed. By 
default, image-cache-eviction-delay is 1800, so what happens to the 
memory usage if you leave Emacs for half an hour?




___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: reproducible memory problem and crashes on cygwin

2006-07-10 Thread emacs user





From: [EMAIL PROTECTED] (Kim F. Storm)
Jason Rumney [EMAIL PROTECTED] writes:

 emacs user wrote:
 an example:

 before editing the image: 33Mb
 during: 39Mb
 after killing the buffer: 39Mb
 image file is 186263 bytes large (jpeg)

 Emacs needs to decompress your jpeg image to display it, and rather
 than do that every time it gets displayed, it caches the decompressed
 image for image-cache-eviction-delay seconds after it was last
 displayed. By default, image-cache-eviction-delay is 1800, so what
 happens to the memory usage if you leave Emacs for half an hour?

Or try this:

M-: (clear-image-cache t) RET


thanks   so I get nil in the echo area and the memory usage does not 
change at all when I try this.  I didnt try leaving emacs for 1/2 an hour.  
it normally crashes with a segmentation something much earlier.

EU

_
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/




___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: reproducible memory problem and crashes on cygwin

2006-07-10 Thread Luc Teirlinck
emacs user wrote:
   
   I'll take your word for that, I hardly know what GC is...

I did not follow this thread and I do not know whether this has
already been pointed out to you, but you can force a garbage
collection using

M-: (garbage-collect)

If by any chance you then see `nil' in the echo area, we know what the
problem is (pure space overflow).  Actually, you can do `M-x garbage-collect'
to force garbage collection, but then you do not see the return value in
the echo area.

Sincerely,

Luc.



___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: reproducible memory problem and crashes on cygwin

2006-07-10 Thread emacs user

From: Luc Teirlinck [EMAIL PROTECTED]

emacs user wrote:

   I'll take your word for that, I hardly know what GC is...

I did not follow this thread and I do not know whether this has
already been pointed out to you, but you can force a garbage
collection using

M-: (garbage-collect)

If by any chance you then see `nil' in the echo area, we know what the
problem is (pure space overflow).  Actually, you can do `M-x 
garbage-collect'

to force garbage collection, but then you do not see the return value in
the echo area.


thanks for this...   so when I do this after killing the image buffers I get 
in the echo area:


((201785 . 16002) (29710 . 0) (1424 . 383) 3020224 374951 (873 . 247) (676 . 
67) (57159 . 8298))


but the memory use does not change.

_
Is your PC infected? Get a FREE online computer virus scan from McAfee® 
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963




___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: reproducible memory problem and crashes on cygwin

2006-07-10 Thread Nick Roberts
  thanks   so I get nil in the echo area and the memory usage does not 
  change at all when I try this.  I didnt try leaving emacs for 1/2 an hour.  
  it normally crashes with a segmentation something much earlier.

Spontaneously?  If you post a backtrace as Eli suggested (as described with
M-x report-emacs-bug), someone might be able to understand the problem.

-- 
Nick   http://www.inet.net.nz/~nickrob


___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


reproducible memory problem and crashes on cygwin

2006-07-09 Thread emacs user

this problem leads to consistent and reproducible crashes of emacs.

using latest cvs gnu emacs (22.0.50) on latest cygwin.

start with
emacs -q --no-site-file
edit a jpeg file
kill buffer
edit another jpeg file
kill buffer again.

every such jpeg file edited and exited leaves the memory used by emacs (as 
seen in the list of processes of the windows task manager) increased.  
Memory does not decrease once buffer with image is killed.  when a text file 
is edited and exited, the memory does return to its original size.


EU

_
Don’t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/




___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug