Bug 357602 - open or open then closed, causes lumina to reset with "out of swap space"
Summary: open or open then closed, causes lumina to reset with "out of swap space"
Status: RESOLVED NOT A BUG
Alias: None
Product: choqok
Classification: Applications
Component: general (show other bugs)
Version: 1.5
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: Mehrdad Momeny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-06 00:32 UTC by rdmyers.42
Modified: 2016-01-06 14:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rdmyers.42 2016-01-06 00:32:42 UTC
either open and running, or open then closed, after an hour causes pcBSD lumina desktop to reset.

The dmesg entry is as follows;

wap_pager_getswapspace(16): failed
swap_pager_getswapspace(4): failed
swap_pager_getswapspace(16): failed
swap_pager_getswapspace(16): failed
swap_pager_getswapspace(16): failed
swap_pager_getswapspace(16): failed
swap_pager_getswapspace(16): failed
swap_pager_getswapspace(16): failed
swap_pager_getswapspace(16): failed
swap_pager_getswapspace(16): failed
swap_pager_getswapspace(16): failed
pid 19129 (Lumina-DE), uid 1001, was killed: out of swap space
pid 17474 (PCDM-session), uid 0: exited on signal 11
pid 19141 (fluxbox), uid 1001: exited on signal 6
pid 79754 (lumina-open), uid 1001: exited on signal 6
pid 19441 (lumina-open), uid 1001: exited on signal 6
pid 68050 (lumina-open), uid 1001: exited on signal 6
pid 19768 (lumina-open), uid 1001: exited on signal 6
pid 24635 (lumina-open), uid 1001: exited on signal 6

can't find any other log entry

Reproducible: Always

Steps to Reproduce:
1. open choqok (or open then close)
2. let sit for an hour
3.  lumina resets

Actual Results:  
have to log back into Lumina

Expected Results:  
Software should no cause window manager to reset
Comment 1 Mehrdad Momeny 2016-01-06 02:25:47 UTC
I really doubt if it has anything to do with Choqok, specially when you have already closed Choqok previously and it's not running anymore.
Comment 2 rdmyers.42 2016-01-06 04:01:28 UTC
Since that is the only program that displays this behaviour, I would disagree
Comment 3 Andrea Scarpino 2016-01-06 12:19:12 UTC
Choqok could be the program that *trigger* this behaviour, but doesn't look like a Choqok issue.

I mean, since you logged something about swap, *maybe* Choqok uses swap space on your system and for some weird reason (to be investigated) when something uses swap your system restarts.
Comment 4 rdmyers.42 2016-01-06 14:22:38 UTC
understand that statement.

please close