Opened 11 years ago
Last modified 10 years ago
#45247 new defect
python2{6,7} memory leak due to db46
| Reported by: | Schamschula (Marius Schamschula) | Owned by: | jyrkiwahlstedt |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.1 |
| Keywords: | Cc: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez), cooljeanius (Eric Gallager), petrrr | |
| Port: | python27 python26 |
Description
http://bugs.python.org/issue22534 points out a situation, where the MacPorts build of python27 which depends on Berkeley db version 4.6, causes a memory leak. The solution is to build against Berkeley db 4.7 instead. The attached patch makes this change.
Attachments (2)
Change History (11)
comment:1 follow-up: 2 Changed 11 years ago by neverpanic (Clemens Lang)
comment:2 Changed 11 years ago by Schamschula (Marius Schamschula)
Replying to cal@…:
Any reason why we're not going for db48 right away?
Nope. So I bumped it in the diff file.
Changed 11 years ago by Schamschula (Marius Schamschula)
| Attachment: | Portfile-python27.diff added |
|---|
comment:3 Changed 11 years ago by jyrkiwahlstedt
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
done in r126081
comment:4 follow-up: 5 Changed 11 years ago by larryv (Lawrence Velázquez)
Does this affect python26 also?
Changed 11 years ago by larryv (Lawrence Velázquez)
| Attachment: | python26-db48.patch added |
|---|
use db48 with python26
comment:5 Changed 11 years ago by larryv (Lawrence Velázquez)
| Cc: | mcalhoun@… added |
|---|---|
| Port: | python26 added |
| Resolution: | fixed |
| Status: | closed → reopened |
| Summary: | python27 memory leak due to db46 → python2{6,7} memory leak due to db46 |
comment:8 Changed 10 years ago by petrrr
| Owner: | changed from macports-tickets@… to jwa@… |
|---|---|
| Status: | reopened → new |
This is probably solved. Assigning to maintainer of python27 for review.
comment:9 Changed 10 years ago by petrrr
| Cc: | jwa@… removed |
|---|
Note: See
TracTickets for help on using
tickets.

Any reason why we're not going for db48 right away?