search for: optimal

Displaying 20 results from an estimated 4177 matches for "optimal".

2017 Jun 27
0
Seg Fault memory violation
Greetings all, Recently ran into a seg fault the keeps reoccurring whenever R-java is used (I believe). Not sure if this is an R issue or an openjdk issue so I'm trying to cover all bases with this report. I tried downgrading R version from 3.4.0 to 3.3.3 with the same results. Also tried downgrading java version from 1.8 to 1.7 with no luck. Running on a fully updated CentOS 7 x86_64,
2017 Dec 06
1
[Gluster-devel] Crash in glusterd!!!
Hi Atin, Please find the backtrace and logs files attached here. Also, below are the BT from core. (gdb) bt #0 0x00003fff8834b898 in __GI_raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x00003fff88350fd0 in __GI_abort () at abort.c:89 [**ALERT: The abort() might not be exactly invoked from the following function line. If
2017 Dec 06
1
[Gluster-devel] Crash in glusterd!!!
I hope these logs were sufficient... please let me know if you require more logs. On Wed, Dec 6, 2017 at 3:26 PM, ABHISHEK PALIWAL <abhishpaliwal at gmail.com> wrote: > Hi Atin, > > Please find the backtrace and logs files attached here. > > Also, below are the BT from core. > > (gdb) bt > > #0 0x00003fff8834b898 in __GI_raise (sig=<optimized out>) at >
2009 Jul 14
9
Opencanvas 1.1b72 issues..
I''ve checked the application database and it apparently ''works'', however, whenever I use it.. Well, I suppose I better get a screenshot of this weirdness to explain. http://img510.imageshack.us/img510/5865/screenshotxmi.png Look at the bottom.. see the squiggly line? Yeah, that''s what''s being drawn, and my cursor is waaaay far away
2008 Jun 05
4
[Bug 16241] New: assertion failed: (movie->cache_state <= SWFDEC_MOVIE_INVALID_CHILDREN)
http://bugs.freedesktop.org/show_bug.cgi?id=16241 Summary: assertion failed: (movie->cache_state <= SWFDEC_MOVIE_INVALID_CHILDREN) Product: swfdec Version: git Platform: x86-64 (AMD64) URL: http://www.cnn.com/ELECTION/2008/primaries/results/score
2013 Mar 16
8
crash with dovecot 2.2: Panic: Buffer full
Hi Timo, I''ve got a crash with dovecot 2.2 dovecot --version 2.2.rc2 (69c26a9e3be5) It''s occured when accessing with imap on a large mailbox (around 50k messages) imap(clean-quarantine at spamguard.fr): Panic: Buffer full (4254 > 4248, pool <none>) Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x6089a) [0x7f9d1bcde89a] ->
2017 Dec 06
1
[Gluster-devel] Crash in glusterd!!!
Without the glusterd log file and the core file or the backtrace I can't comment anything. On Wed, Dec 6, 2017 at 3:09 PM, ABHISHEK PALIWAL <abhishpaliwal at gmail.com> wrote: > Any suggestion.... > > On Dec 6, 2017 11:51, "ABHISHEK PALIWAL" <abhishpaliwal at gmail.com> wrote: > >> Hi Team, >> >> We are getting the crash in glusterd after
2013 Mar 07
4
[dovecot-2.1.15] mdbox corruption, doveadm force-resync can't repair it (throws segfault)
Hi Timo, hi all! Today i noticed imap throws segmentation faults and dumps cores. I looked into logs I can see: 2013-03-07T12:12:52.257986+01:00 meteor dovecot: imap(marcinxxx at kolekcja.mejor.pl) <7sRXtFPXYAA+eX93>: Error: Corrupted dbox file /dane/domeny/mejor.pl/mail/marcin//.mdbox/mailinglists/storage/m.75 (around offset=2779212): EOF reading msg
2011 Apr 27
2
btrfs-convert crashes
I have a 1.5 TB (1,475,720,773,632) partition that I wanted to convert from ext4 to btrfs. It is currently used as / for ubuntu 10.10. I booted into 11.04 beta2 and tried a ''btrfs-convert /dev/sdc1'', but after about 20 minutes it segfaulted. I performed a: sck.ext4 -cDfty -C 0 /dev/sdc1 After everything was clean, I downloaded the debugging symbols for
2013 Sep 10
1
Dovecot 2.0, 2.1 and 2.2.5 core dump when Quota Plugin (FS) is enabled
Hi, we are actually deploying a new IMAP-Server, targeting dovecot 2.1.17. Unfortunately, our tests with imaptest did not succeed, were ending in core dumps. We did this test: ./imaptest host=example.com port=143 user=strack pass=secret disconnect_quit no_pipelining mbox=dovecot-crlf That''s what we get in dovecot''s log: Sep 10 11:17:04 imap-login: Info: Login:
2012 Jun 15
3
doveadm backup panic
using latest auto build didn''t help. this happens only with a specific account. # doveadm -o imapc_user=----- at domain.com -o imapc_password=---- backup -u =----- at domain.com -R imapc: dsync(---- at domain.com): Panic: pool_data_stack_realloc(): stack frame changed dsync(---- at domain.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x4209a)
2008 May 28
1
[Bug 15962] New: Crash with flashblock
http://bugs.freedesktop.org/show_bug.cgi?id=15962 Summary: Crash with flashblock Product: swfdec Version: git Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: critical Priority: medium Component: plugin AssignedTo: swfdec at lists.freedesktop.org ReportedBy:
2013 Sep 06
8
Re: [Gluster-devel] GlusterFS 3.3.1 client crash (signal received: 6)
It''s a pity I don''t know how to re-create the issue. While there are 1-2 crashed clients in total 120 clients every day. Below is gdb result: (gdb) where #0 0x0000003267432885 in raise () from /lib64/libc.so.6 #1 0x0000003267434065 in abort () from /lib64/libc.so.6 #2 0x000000326746f7a7 in __libc_message () from /lib64/libc.so.6 #3 0x00000032674750c6
2018 Apr 06
2
[RFC] Adding function attributes to represent codegen optimization level
On Thu, Apr 5, 2018 at 8:44 AM, via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 2018-04-04 22:00, Mehdi AMINI wrote: > >> Le mar. 3 avr. 2018 à 12:47, via llvm-dev <llvm-dev at lists.llvm.org> a >> écrit : >> >> All, >>> A recent commit, D43040/r324557, changed the behavior of the gold >>> plugin >>> when compiling
2018 Apr 03
2
[RFC] Adding function attributes to represent codegen optimization level
All, A recent commit, D43040/r324557, changed the behavior of the gold plugin when compiling with LTO. The change now causes the codegen optimization level to default to CodeGenOpt::Default (i.e., -O2) rather than use the LTO optimization level. The argument was made that the LTO optimization level should control the amount of cross-module optimizations done by LTO, but it should not
2018 Apr 05
1
[RFC] Adding function attributes to represent codegen optimization level
Le mar. 3 avr. 2018 à 12:47, via llvm-dev <llvm-dev at lists.llvm.org> a écrit : > All, > A recent commit, D43040/r324557, changed the behavior of the gold plugin > when compiling with LTO. The change now causes the codegen optimization > level to default to CodeGenOpt::Default (i.e., -O2) rather than use the > LTO optimization level. The argument was made that the LTO
2018 Apr 05
1
[RFC] Adding function attributes to represent codegen optimization level
On 2018-04-04 22:00, Mehdi AMINI wrote: > Le mar. 3 avr. 2018 à 12:47, via llvm-dev <llvm-dev at lists.llvm.org> a > écrit : > >> All, >> A recent commit, D43040/r324557, changed the behavior of the gold >> plugin >> when compiling with LTO. The change now causes the codegen >> optimization >> level to default to CodeGenOpt::Default (i.e.,
2010 Jan 28
0
assertion mail-transaction-log-view.c
I''m not sure how useful this is with optimization turned back on, but here it is anyway. This was just a one off that happened last night: Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): fscking index file /rci/nqu/rci/u2/user/dovecot/.INBOX/dovecot.index Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): Panic: file
2017 Aug 24
2
JIT Optimization Levels
Hello, there are several optimization levels in lli like O0, O1, O2, O3. What does they mean? how the run time optimization is performed in LLVM JIT? I am working on a project where my goal is to study the impact of lli optimizations. here my IR is already optimized through opt. now i have to perform lli optimizations provided i am giving varying inputs at run time. so i suppose here my
2006 Aug 03
2
Index.optimize
In the documentation, it says that optimize "should only be called when the index will no longer be updated very often, but will be read a lot". Does this mean it actually has a detrimental impact on updates and inserts? In my project there will be many more reads than updates, but there will still be a lot of updates. So should I be calling Optimize once a day or something like that,