[Mono-bugs] [Bug 669519] New: Crash when using 64-bit Mono, works with 32-bit

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Fri Feb 4 06:46:41 EST 2011



           Summary: Crash when using 64-bit Mono, works with 32-bit
    Classification: Mono
           Product: Mono: Runtime
           Version: 2.8.x
          Platform: x86-64
        OS/Version: Ubuntu
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: misc
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: refic at psimerion.org
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b10) Gecko/20100101

The MJ12 distributed www crawler crashes every time after uploading a finished
work unit back to the project's servers. This only happens with 64-bit Mono,
32-bit version works just fine. Also this didn't happen with Mono 2.4, it
started happening with 2.6 and is still happening with current git head.

There is no stacktrace, the only thing it says is: "Stacktrace: <empty line>
Native stacktrace: <empty line> Segmentation fault (core dumped)". There seems
to be some Apport generated crash dump in /var/crash, please let me know if
you'd like to take a look at it, or if there is any other way I can help
solving the problem.

This bug has been confirmed by many of the project users with many different
setups. It's always the 64-bit version of Mono that crashes.

Reproducible: Always

Steps to Reproduce:
1. Use a 64-bit Mono
2. Run the client
(http://www.majestic12.co.uk/files/mj12node/mono/mj12node_linux_v170b2.tgz) -
you need to create an account though.
3. Let it run until it finishes a work unit and starts to upload it back to
4. The client crashes right after finishing the upload.
Actual Results:  

Expected Results:  
Continue working.

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list