| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
3051
|
07 Jun 2025 |
Mark Grimes | Bug Report | Memory leak in mhttpd binary RPC code | Hi,
We applied an intermediate fix
for this locally and it seems to have fixed |
|
|
3055
|
10 Jun 2025 |
Konstantin Olchanski | Bug Report | Memory leak in mhttpd binary RPC code | I confirm that MJSON_ARRAYBUFFER does not
work correctly for zero-size buffers,
buffer is leaked in the destructor and copied |
|
|
3058
|
15 Jun 2025 |
Mark Grimes | Bug Report | Memory leak in mhttpd binary RPC code | Many thanks for the fix. We've applied and
see better memory performance. We still
have to kill and restart
|
|
|
3061
|
23 Jun 2025 |
Stefan Ritt | Bug Report | Memory leak in mhttpd binary RPC code | Since this memory leak is quite obvious, I
pushed the fix to develop.
|
|
|
637
|
06 Sep 2009 |
Exaos Lee | Bug Fix | Maybe a fix | Changing "SQLINTEGER" to "SQLLEN" maybe let
the compiling pass. See the attached diff.
|
|
|
2380
|
31 Mar 2022 |
Stefan Ritt | Suggestion | Maximum ODB size | Anybody some idea what the maximum ODB size
can be? In the old days, the linux
kernels had a severe limit on shared memory |
|
|
2381
|
04 Apr 2022 |
Konstantin Olchanski | Suggestion | Maximum ODB size | > Anybody some idea what the maximum ODB size
can be?
|
|
|
2476
|
27 Apr 2023 |
Marius Koeppel | Suggestion | Maximum ODB size | Hi all,
> I agree, I think we can safely bump the |
|
|
2477
|
27 Apr 2023 |
Konstantin Olchanski | Suggestion | Maximum ODB size | > > I agree, I think we can safely bump the
limit from 100 Mbytes to 1 Gbyte, maybe 1.5
or
|
|
|
2480
|
27 Apr 2023 |
Marius Koeppel | Suggestion | Maximum ODB size | > This is change is wrong. As I wrote, ODB
is not 64-bit clean and it is not 32-bit
clean. We think is is 31-bit clean, so maximum |
|
|
2481
|
27 Apr 2023 |
Konstantin Olchanski | Suggestion | Maximum ODB size | > You said the writing into .odb is buggy.
Do you mean it’s buggy in general or only
in this specific case?
|
|
|
2482
|
27 Apr 2023 |
Konstantin Olchanski | Suggestion | Maximum ODB size | my vote is to bump the ODB size limit to 1999*1000*1000
(not quite 2GB). but this needs to be tested.
especially save and restore from ODB, XML |
|
|
2483
|
27 Apr 2023 |
Stefan Ritt | Suggestion | Maximum ODB size | > Congratulations. created != "it works".
Two other tings to consider:
|
|
|
2485
|
28 Apr 2023 |
Marius Koeppel | Suggestion | Maximum ODB size | > my vote is to bump the ODB size limit to
1999*1000*1000 (not quite 2GB). but this
needs to be tested. especially save and restore |
|
|
2486
|
28 Apr 2023 |
Stefan Ritt | Suggestion | Maximum ODB size | > Is this maybe related to what Stefan said
about the run start - so that odbedit needs
some time to load the bigger ODB?
|
|
|
2487
|
28 Apr 2023 |
Marius Koeppel | Suggestion | Maximum ODB size | > At the run start mlogger writes the ODB
to the .mid file. This needs conversion (binary
ODB -> XML ASCII) which can take time.
|
|
|
2488
|
28 Apr 2023 |
Konstantin Olchanski | Suggestion | Maximum ODB size | > > Congratulations. created != "it works".
>
> Two other tings to consider:
|
|
|
2489
|
28 Apr 2023 |
Konstantin Olchanski | Suggestion | Maximum ODB size | > > Is this maybe related to what Stefan said
about the run start - so that odbedit needs
some time to load the bigger ODB?
|
|
|
2525
|
09 Jun 2023 |
Konstantin Olchanski | Suggestion | Maximum ODB size | > > 1) The ODB shared memory is dumped into
a binary file (".ODB.SHM") after the last
client finished ...
|
|
|
2527
|
12 Jun 2023 |
Stefan Ritt | Suggestion | Maximum ODB size | > correction: ODB shared memory is saved to
.ODB.SHM each time a client stops, this is
db_close_database().
|
|