Ask / Submit
8

Lipstick eating lot of ram while downloading big files via stock browser

asked 2014-06-28 21:23:24 +0200

Mądry gravatar image

updated 2014-07-23 22:24:55 +0200

Recently I tried to download big archive ( it was packed rom for ppsspp test ) which weighed about 400MB via sailfish browser. After a while jolla became unresponsive. I checked the actual memory use SailTime and found out that both ram and swap were almost filled ( about 98% each). Then fired up Lighthouse and the source of the problem turned out to be lipstick taking about 40-50% of ram and probably most of the swap. The problem is that after started download phone almost immediately slows down and even closing all of apps doesn't help. Stopping the download doesn't help too and lipstick constantly eats ram until I restart the whole service via patchmanager. Issue seems to be not related to size of the file because even 90MB archive of gapps made my jolla struggle for resources. I remember that before last update I hadn't such issues and downloading few archives of pictures from onedrive each about 160MB of size didn't even make my jolla ”sweat„. Yesterday I resetted jolla and again updated to Saapunki 1.0.7.16 but the problem remains even after reboot until I remove/stop the transfer in settings. Does anybody have such issues ?

edit 23-7-2014: Latest 1.0.8.19 Tahkalampi update didn't change anything. Still, any download via sailfish browser causes memory leak in lipstick. Downloading 32MB archive from dropbox made lipstick grow in ram from 13% to 25%.

edit retag flag offensive close delete

Comments

Also worth mentioning that the same issue occurs while downloading via webcat browser. Transfer isn't showed in settings but lipstick acts the same way.

Mądry ( 2014-06-29 00:18:26 +0200 )edit

Does the same happen in Android firefox?

rainisto ( 2014-06-29 10:27:12 +0200 )edit

No. Android firefox seems to not cause any memory leak in lipstick or even in its own process. It seems to be related only to qt based software and not even the browser (which can be closed but downloading doesn't stop) but the transfer part of the settings app which handle the downloads.

Mądry ( 2014-06-29 12:13:49 +0200 )edit

what was the file extension of downloaded file? .zip, .rar, apk or .rom or something else?

rainisto ( 2014-06-30 09:19:38 +0200 )edit

I were downloading only zip archives: zipped photos of notes(160MB), gapps(90MB) and zipped rom(450MB). In all cases lipstick was going crazy, eating ram in pair with downloaded data. Once i thought the problem was in the priority to write stuff to flash memory but the size of downloading file grows while data is downloading. I must mention that I don't use any microsd card and till now I used only 5 gigs of jolla's internal memory.

Mądry ( 2014-06-30 10:52:07 +0200 )edit

1 Answer

Sort by » oldest newest most voted
2

answered 2014-06-28 22:07:11 +0200

rainisto gravatar image

updated 2014-06-30 13:40:32 +0200

I suggest using curl when downloading big files.

PS. I created entry to internal bugzilla for this.

PS2. curl is just my personal preference on downloading big files, as it has support for resume disconnected transfers etc.

Example command:

curl --progress-bar http://caesar.acc.umu.se/debian-cd/7.5.0/i386/iso-cd/debian-update-7.5.0-i386-CD-9.iso -o debian-update-7.5.0-i386-CD-9.iso
edit flag offensive delete publish link more

Comments

1

Hmm...nice. Curl already installed and available from terminal. Still bothers me the fact that before some update I hadn't such issues. I'll try to make use of curl.

Mądry ( 2014-06-28 22:16:08 +0200 )edit
2

And instead of browser you would suggest to use links2. Maybe if curl can handle it you should use it in browser, instead if suggesting it to end user?

ZogG ( 2014-06-29 08:56:47 +0200 )edit
2

@ZogG : What is the problem with offering the user a solution to his problem, until it has been confirmed and a bug fix made?

Philippe De Swert ( 2014-06-30 10:36:20 +0200 )edit
1

I appreciate every help here offered, but the fact is that I never used curl before ( only few times wget ) and it may be a little problematic to use it in some sort of replacement to system's downloader. Yesterday I succesfully downloaded the same 400MB archive with android firefox but I think it wasn't the best solution. Firefox took about 200MB from ram. It's download manager doesn't even show the progress of downloading.

Mądry ( 2014-06-30 11:20:13 +0200 )edit

So we need to enable developer mode that contains security/privacy/possible battery issues to download files? Not good.

vasavr ( 2014-06-30 19:37:05 +0200 )edit
Login/Signup to Answer

Question tools

Follow
1 follower

Stats

Asked: 2014-06-28 21:23:24 +0200

Seen: 854 times

Last updated: Jul 23 '14