Bug 25728 - Crash due to glibc detected memory corruption
Summary: Crash due to glibc detected memory corruption
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Runtime
Classification: Mono
Component: Interop ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-01-05 18:30 UTC by Nick
Modified: 2015-03-30 15:08 UTC (History)
5 users (show)

Tags: glibc crash pango cairo gui
Is this bug a regression?: ---
Last known good build:


Attachments
crash1.log (18.36 KB, application/octet-stream)
2015-01-05 18:30 UTC, Nick
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NOT_ON_ROADMAP

Description Nick 2015-01-05 18:30:08 UTC
Created attachment 9248 [details]
crash1.log

General description:

Running a GUI application that reads files, processes then and writes new files. As files are processed GUI displays the file name and a progress bar. 

Expected: 

 Application should finished running without crashing.

What happens: 

Application crashes intermittently (about 1 in 10 times) with a stack trace from C code. Can only reproduce so far a second Mono GUI application running on the same Desktop. In this case MonoDevelop.

See attached crash1.log file for stack trace and how Application was started. Replaced name of executable with <EXE>.


System info:

 CentOS 6.5 64bit
  
 $ mono --version 
Mono JIT compiler version 3.10.0 (tarball Sat Oct  4 15:25:02 UTC 2014)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
        TLS:           __thread
        SIGSEGV:       altstack
        Notifications: epoll
        Architecture:  amd64
        Disabled:      none
        Misc:          softdebug 
        LLVM:          yes(3.4svn-mono-/)
        GC:            sgen

Additional info:

 * Application was started with --debug flag to see it would print extra info. But it was crashing without the --debug just as much.

 * MonoDevelop 5.7 was up and running in the background in a different windows on the same Desktop. If MonoDevelop is not up could not reproduce the crash. Mentioning it just because this might be significant.
Comment 1 Zoltan Varga 2015-01-08 04:55:35 UTC
This is a windows.forms application, and mono no longer supports windows.forms.