Hi SQLite team,
I have been using the System.Data.SQLite.dll (1.0.111.0) and System.Data.SQLite.Linq.dll (1.0.111.0) assemblies in my .NET Framework 3.5 SP1 application. SQLite database has 4 tables in it. Each table will be inserted with more than 50 data at once. When the data for all the tables is inserted for more than 20 times continuously, *System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt error* will occur and data will not be saved to database. *More Information about Exception*: Exception Occurred System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at System.Security.FrameSecurityDescriptor.CheckSetDemand2(PermissionSet demandSet, PermissionSet& alteredDemandSet, RuntimeMethodHandle rmh, Boolean fDeclarative) at System.Security.FrameSecurityDescriptor.CheckSetDemand(PermissionSet demandSet, PermissionSet& alteredDemandSet, RuntimeMethodHandle rmh) at System.Security.SecurityRuntime.FrameDescSetHelper(FrameSecurityDescriptor secDesc, PermissionSet demandSet, PermissionSet& alteredDemandSet, RuntimeMethodHandle rmh) at lambda_method(ExecutionScope , Object ) --- End of inner exception stack trace --- at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) at System.Delegate.DynamicInvokeImpl(Object[] args) at DbLinq.Data.Linq.Sugar.ParameterizedQuery.GetCommandTransactional(Boolean createTransaction) at DbLinq.Data.Linq.Sugar.ParameterizedQuery.GetCommand() at DbLinq.Data.Linq.Sugar.Implementation.QueryRunner.Upsert(Object target, UpsertQuery insertQuery) at DbLinq.Data.Linq.Sugar.Implementation.QueryRunner.Insert(Object target, UpsertQuery insertQuery) at DbLinq.Data.Linq.DataContext.InsertEntity(Object entity, QueryContext queryContext) at DbLinq.Data.Linq.DataContext.SubmitChangesImpl(ConflictMode failureMode) at DbLinq.Data.Linq.DataContext.SubmitChanges(ConflictMode failureMode) Earlier, I was using 1.0.103.0 version assemblies and noticed the same behavior. Issue occurs in the latest version as well. Application will perform some operation and will insert the data continuously to database. Few data will be skipped to save because of the exception. Please help me out with this issue or let me know any workaround that can fix this issue. Let me know if you need any logs information. Thank you, Regards, Vishruth -- *DISCLAIMER:*This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee, copying, dissemination, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. Any views or opinions presented in this email are solely those of the author and do not necessarily represent the organization. Employees of Utthunga Technologies Pvt. Ltd. are expressly instructed not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to Utthunga's policy and outside the scope of the employment of the individual concerned and Utthunga will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. Utthunga accepts no liability for any damage caused by any virus transmitted by this email. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
