[Mono-bugs] [Bug 658249] New: DataTable GetChanges() or AcceptChanges() causes a timeout
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Wed Dec 8 09:26:48 EST 2010
https://bugzilla.novell.com/show_bug.cgi?id=658249
https://bugzilla.novell.com/show_bug.cgi?id=658249#c0
Summary: DataTable GetChanges() or AcceptChanges() causes a
timeout
Classification: Mono
Product: Mono: Class Libraries
Version: 2.8.x
Platform: x86-64
OS/Version: openSUSE 11.3
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Sys.Data
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: aldo.prinzi at docubox.it
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Blocker: ---
Created an attachment (id=403936)
--> (http://bugzilla.novell.com/attachment.cgi?id=403936)
Code to reproduce problem
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; it; rv:1.9.2.12)
Gecko/20101026 Firefox/3.6.12
My program is on production by more than one year and works well on Windows and
ond older (older than 2.8.x) versions of Mono.
I have a System.Data.DataTable filled with big string data.
It hangs when I need to check for changes or AcceptChages() before persist it
on file.
I have done several test to reproduce the problem, and I have attached code to
reproduce it
Reproducible: Always
Steps to Reproduce:
See attached code
Actual Results:
On Windows (.net 2.0)
1) 15:04:20 2) 0,0624sec 3) 9,4380sec 4) 9,4380sec
On MONO (2.8.1 using VmWare Virtual Machine downloaded from the site, with
OpenSuse, but I have the same problem on Slackware 13/64)
1) 14:58:00 2) 0.0339sec bash: line 1: 4271 Killed
/usr/bin/mono --debug
--debugger-agent=transport=dt_socket,address=127.0.0.1:33678
"/root/Projects/AdoTest/AdoTest/bin/Debug/AdoTest.exe"
Expected Results:
No error.
At this time to let the program be executed I have removed the AcceptChanges()
statement from my code.
--
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