search

mgansler / mscgen

Automatically exported from code.google.com/p/mscgen
GNU General Public License v2.0
1 stars 0 forks source link

mscgen regression in svn (infinite loop) #56

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Hi

Attached is a msc file that mscgen 0.18 handles without issues; however mscgen 
revision 166 does not seem to complete the image generation. Note I have not 
tested other revisions (beyond the 0.18 from Debian's archive).

I tried both with -Tpng and -Tsvg. -Tpng nearly makes my system freeze, so I 
can recommend testing with -Tsvg that is some what kinder to the system.

Using strace I came to the conclusion that mscgen enters an infinite memory 
reallocation loop[1]; but I am not sure why or where in the code it happens.

~Niels

[1]
...
brk(0x1654d000)                         = 0x1654d000
mremap(0xb618a000, 18116608, 18120704, MREMAP_MAYMOVE) = 0xb618a000
mremap(0xb618a000, 18120704, 18124800, MREMAP_MAYMOVE) = 0xb618a000
mremap(0xb618a000, 18124800, 18128896, MREMAP_MAYMOVE) = 0xb618a000
brk(0x1656e000)                         = 0x1656e000
mremap(0xb618a000, 18128896, 18132992, MREMAP_MAYMOVE) = 0xb618a000
mremap(0xb618a000, 18132992, 18137088, MREMAP_MAYMOVE) = 0xb618a000
mremap(0xb618a000, 18137088, 18141184, MREMAP_MAYMOVE) = 0xb618a000
brk(0x1658f000)                         = 0x1658f000
mremap(0xb618a000, 18141184, 18145280, MREMAP_MAYMOVE) = 0xb618a000
mremap(0xb618a000, 18145280, 18149376, MREMAP_MAYMOVE) = 0xb618a000
^C--- SIGINT (Interrupt) @ 0 (0) ---

Original issue reported on code.google.com by NThykier@gmail.com on 13 Nov 2010 at 1:51

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by NThykier@gmail.com on 13 Nov 2010 at 1:52

GoogleCodeExporter commented 8 years ago

Original comment by Michael....@gmail.com on 13 Nov 2010 at 4:32

GoogleCodeExporter commented 8 years ago 
This issue was closed by revision r167.

Original comment by Michael....@gmail.com on 14 Nov 2010 at 12:25

GoogleCodeExporter commented 8 years ago 
Yup - that's a nasty bug which goes on growing memory indefinitely.

Sorry for that one & thanks for reporting - it's fixed now.

Original comment by Michael....@gmail.com on 14 Nov 2010 at 12:26