WineHQ Bugzilla – Bug 32617 – eMule keeps tens of thousands of open files making linux crash

Bugzilla

Last modified: 2017-03-10 05:55:42 UTC

eMule keeps tens of thousands of open files making linux crash

Bug 32617 - eMule keeps tens of thousands of open files making linux crash


Summary:	eMule keeps tens of thousands of open files making linux crash

Status:	CLOSED ABANDONED

AppDB:	Show Apps affected by this bug
Product:	Wine
Classification:	Unclassified
Component:	-unknown
Version:	1.5.17
Hardware:	x86 Linux

Importance:	P2 normal
Target Milestone:	---
Assigned To:	Mr. Bugs

URL:
Keywords:	Abandoned?, regression

Depends on:
Blocks:
	Show dependency tree

Reported:	2012-12-31 16:06 UTC by Federico
Modified:	2017-03-10 05:55 UTC (History)
CC List:	0 users

See Also:
Regression SHA1:
Fixed by SHA1:
Distribution:	---
Staged patchset:

Attachments
lsof \| grep -i emule (52.96 KB, application/x-7z-compressed) 2012-12-31 16:06 UTC, Federico	Details
View All Add an attachment (back traces, logs, proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Federico 2012-12-31 16:06:22 UTC

Created attachment 43043 [details]
lsof | grep -i emule

Most of the open files in my machine are from eMule: right now about 40k and it's two instances of eMule, but I sometimes reach half a million open files and I guess it's eMule's fault again. This used not to happen with previous versions of wine and same version of eMule; I'm using wine 1.5.17 now.

$ cat /proc/sys/fs/file-nr
146048  0       371898
$ uname -a
Linux e350 3.6.10-2.fc17.i686.PAE #1 SMP Tue Dec 11 18:27:35 UTC 2012 i686 i686 i386 GNU/Linux

Comment 1 Austin English 2012-12-31 19:47:17 UTC

Please run a regression test

Comment 2 Federico 2012-12-31 20:10:59 UTC

(In reply to comment #1)
> Please run a regression test

It would take ages, it takes several hours for the thing to become noticeable; does git bisect work with reboots? And most importantly, what good and bad versions should I start with?
Are there rpms for some close versions I could use for testing instead?

Comment 3 Austin English 2012-12-31 22:14:40 UTC

(In reply to comment #2)
> (In reply to comment #1)
> > Please run a regression test
> 
> It would take ages, it takes several hours for the thing to become noticeable;
> does git bisect work with reboots?

Yes.

> And most importantly, what good and bad
> versions should I start with?

Whatever version of wine you last used that didn't have a problem.

Comment 4 Federico 2013-01-14 02:06:26 UTC

I tried regression testing with 1.5.15 as good (which should be correct given the update history and when problems started) and 1.5.17 as bad, but I arrived till the end and I wasn't able to find any good revision: also because I didn't know what to check exactly or if something else was to blame for the crashes; or perhaps because I didn't choose the correct good revision.

Now I've downgraded wine through fedora's repositories and I'm using 1.5.2, everything seems to work again.

Comment 5 Federico 2013-03-29 11:10:47 UTC

I upgraded to fedora 18 and the downgrade to 1.5.2 was overridden: I confirm this is still present with 1.5.24 and makes my machine quickly crash (few hours after boot).

Comment 6 Rosanne DiMesio 2015-02-14 15:15:52 UTC

Is this still an issue in the current development release (1.7.36 or later)?

Comment 7 Ken Sharp 2017-02-22 02:19:40 UTC

Abandoned.

Comment 8 Austin English 2017-03-10 05:55:42 UTC

Closing.