Opened 5 years ago

Closed 3 years ago

Last modified 14 months ago

#15382 closed bug (fixed)

Possible memory leak in webpositive

Reported by: nephele Owned by: pulkomandy
Priority: normal Milestone: R1/beta3
Component: Kits/Web Kit Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

hrev53511

Attached are two screenshots some minutes aport from each other, i did not use the system in the meantime (except to take the two screenshots each)

I checked this out because i had 1.2GB of ram allocated to webpositive for my 4 open tabs, which seamed a bit much.

Reproduce:

  1. open https://discuss.haiku-os.org/ as sole tab
  2. close webpositive and reopen (so it doesn't have any other junk that might falsify this test)
  3. check memory
  4. wait a bit
  5. check memory

Attachments (2)

first.png (181.5 KB ) - added by nephele 5 years ago.
First picture
second.png (179.8 KB ) - added by nephele 5 years ago.
Second picture (taken some minutes after the first one)

Download all attachments as: .zip

Change History (7)

by nephele, 5 years ago

Attachment: first.png added

First picture

by nephele, 5 years ago

Attachment: second.png added

Second picture (taken some minutes after the first one)

comment:1 by tthoms, 4 years ago

After a period of time using WebPositive, the amount of memory used continues to grow. If I run the software for 30 minutes, and then try to run a make of a set of source code, I can consistently lock up the machine.

comment:2 by diver, 4 years ago

Component: - GeneralApplications/WebPositive
Owner: changed from nobody to pulkomandy

comment:3 by Coldfirex, 3 years ago

Still an issue with 1.8.x?

comment:4 by nephele, 3 years ago

Component: Applications/WebPositiveKits/Web Kit
Milestone: UnscheduledR1/beta3
Resolution: fixed
Status: newclosed

comment:5 by cocobean, 14 months ago

Haiku hrev56773 x86 memory leak test:

WebPositive 1.3 alpha
HaikuWebKit 1.9.3 (WebKit 615.1.15)
  • Test time: 170m (almost 3 hours)
  • Memory consumed: 1.5GiB RAM
Note: See TracTickets for help on using tickets.