Hidpi Bug ??????

I work with a new project in adobe muse and I use a 2x resolution but in the web the resolution is normal!!
I have enable the HIDPI resolution in the project !
I use Adobe muse 2014.2.1.284 for windows !
The test for project is in this page : Home
The problem is always with hd screen and also with background image and sigle image!!!
someone can help me?????
Thanks

I noticed that the files in the folder museutil.js script contains functions to determine whether or not that los creen retina or hd.
Analyzing the file I noticed that there must be a bug on the
g.isRetina = function () {
         if (1.5 <= window.devicePixelRatio) return! 0;
         if (window.matchMedia window.matchMedia && ("(- webkit-min-device-pixel-ratio: 1.5), (min - moz-device-pixel-ratio: 1.5), (- o-min-device-pixel -ratio: 3/2), (min-resolution: 1.5dppx) "). matches) return! 0;
         return! 1
because if I change the value from 1.5 to 1 recognizes my screen (1920x1080) as full hd and The image display correctly in HiDPI!
But I will not change this file before you have an opinion of the staff!
I await news

Similar Messages

[bug] workqueue leaked lock or atomic when connecting Apple Trackpad

Hi.
Recently I reported pretty useless bug into archlinux bugtracker about system freezes caused by Apple Magic Trackpad.
https://bugs.archlinux.org/task/37587
I've been able to reproduce it and dump dmesg output to file. Now I need some help in «decoding» info from dmesg to be able to provide more info into bug ticket or even report a bug upstream
Help me decide, please, what component (hid, bluetooth, etc) causes this bug.
I'm not sure, because unloading hid_magicmouse module stops errors in dmesg. Though hci_rx_work [bluetooth] is mentioned in the log.
[ 2723.850822] BUG: workqueue leaked lock or atomic: kworker/u9:0/0xfffffffe/1692
last function: hci_rx_work [bluetooth]
[ 2723.850826] CPU: 1 PID: 1692 Comm: kworker/u9:0 Tainted: P W O 3.12.0-1-ARCH #1
[ 2723.850827] Hardware name: System manufacturer P5K/P5K, BIOS 1006 03/05/2008
[ 2723.850833] Workqueue: hci0 hci_rx_work [bluetooth]
[ 2723.850835] ffff8801a3837000 ffff8801a5239e20 ffffffff814ebffb ffff880037f19d80
[ 2723.850838] ffff8801a5239e68 ffffffff8107dd07 00000000a3837000 ffff88018ccc1500
[ 2723.850842] ffff8801a3837000 ffff8801a3837018 ffff880037f19db0 ffff8800ca8c88b0
[ 2723.850845] Call Trace:
[ 2723.850849] [<ffffffff814ebffb>] dump_stack+0x54/0x8d
[ 2723.850852] [<ffffffff8107dd07>] process_one_work+0x3a7/0x450
[ 2723.850855] [<ffffffff8107e4d1>] worker_thread+0x121/0x3a0
[ 2723.850858] [<ffffffff8107e3b0>] ? manage_workers.isra.23+0x2b0/0x2b0
[ 2723.850862] [<ffffffff81084e60>] kthread+0xc0/0xd0
[ 2723.850865] [<ffffffff81084da0>] ? kthread_create_on_node+0x120/0x120
[ 2723.850868] [<ffffffff814faafc>] ret_from_fork+0x7c/0xb0
[ 2723.850871] [<ffffffff81084da0>] ? kthread_create_on_node+0x120/0x120
[ 2723.850874] BUG: scheduling while atomic: kworker/u9:0/1692/0xffffffff
[ 2723.850875] Modules linked in: hid_magicmouse hidp btusb bnep xt_mac ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter ip_tables x_tables coretemp kvm_intel kvm iTCO_wdt iTCO_vendor_support joydev hid_generic hid_logitech_dj usbhid gpio_ich hid evdev i2c_i801 microcode nvidia(PO) serio_raw lpc_ich snd_hda_codec_realtek snd_ice1724 snd_ak4113 snd_pt2258 snd_ak4114 snd_i2c snd_ice17xx_ak4xxx snd_ak4xxx_adda snd_ac97_codec ac97_bus snd_rawmidi snd_seq_device snd_hda_intel snd_hda_codec atl1 snd_hwdep snd_pcm snd_page_alloc snd_timer snd mii drm soundcore i2c_core shpchp asus_atk0110 intel_agp intel_gtt button processor rfcomm bluetooth rfkill nf_conntrack_ftp nf_conntrack ext4 crc16 mbcache jbd2 sd_mod sr_mod cdrom ata_generic pata_acpi firewire_ohci ata_piix firewire_core
[ 2723.850922] crc_itu_t ahci pata_jmicron libahci libata scsi_mod ehci_pci uhci_hcd ehci_hcd usbcore usb_common [last unloaded: btusb]
[ 2723.850931] CPU: 1 PID: 1692 Comm: kworker/u9:0 Tainted: P W O 3.12.0-1-ARCH #1
[ 2723.850932] Hardware name: System manufacturer P5K/P5K, BIOS 1006 03/05/2008
[ 2723.850937] ffff8801afc944c0 ffff8801a5239d40 ffffffff814ebffb ffff8801a3837000
[ 2723.850940] ffff8801a5239d50 ffffffff814e95a6 ffff8801a5239e58 ffffffff814f15df
[ 2723.850944] 00000000000144c0 ffff8801a5239fd8 ffff8801a5239fd8 00000000000144c0
[ 2723.850947] Call Trace:
[ 2723.850950] [<ffffffff814ebffb>] dump_stack+0x54/0x8d
[ 2723.850954] [<ffffffff814e95a6>] __schedule_bug+0x4d/0x5b
[ 2723.850957] [<ffffffff814f15df>] __schedule+0x93f/0x950
[ 2723.850961] [<ffffffff81016f70>] ? show_stack_log_lvl+0xd0/0x1c0
[ 2723.850964] [<ffffffff81018245>] ? show_stack+0x25/0x50
[ 2723.850967] [<ffffffff8107db4c>] ? process_one_work+0x1ec/0x450
[ 2723.850970] [<ffffffff814f1619>] schedule+0x29/0x70
[ 2723.850973] [<ffffffff8107e578>] worker_thread+0x1c8/0x3a0
[ 2723.850976] [<ffffffff8107e3b0>] ? manage_workers.isra.23+0x2b0/0x2b0
[ 2723.850980] [<ffffffff81084e60>] kthread+0xc0/0xd0
[ 2723.850983] [<ffffffff81084da0>] ? kthread_create_on_node+0x120/0x120
[ 2723.850986] [<ffffffff814faafc>] ret_from_fork+0x7c/0xb0
[ 2723.850989] [<ffffffff81084da0>] ? kthread_create_on_node+0x120/0x120
[ 2723.861820] BUG: workqueue leaked lock or atomic: kworker/u9:0/0xfffffffe/1692
last function: hci_rx_work [bluetooth]
[ 2723.861824] CPU: 1 PID: 1692 Comm: kworker/u9:0 Tainted: P W O 3.12.0-1-ARCH #1
[ 2723.861826] Hardware name: System manufacturer P5K/P5K, BIOS 1006 03/05/2008
[ 2723.861831] Workqueue: hci0 hci_rx_work [bluetooth]
[ 2723.861833] ffff8801a3837000 ffff8801a5239e20 ffffffff814ebffb ffff880037f19d80
[ 2723.861837] ffff8801a5239e68 ffffffff8107dd07 00000000a3837000 ffff88018ccc1500
[ 2723.861840] ffff8801a3837000 ffff8801a3837018 ffff880037f19db0 ffff8800ca8c88b0
[ 2723.861843] Call Trace:
[ 2723.861847] [<ffffffff814ebffb>] dump_stack+0x54/0x8d
[ 2723.861850] [<ffffffff8107dd07>] process_one_work+0x3a7/0x450
[ 2723.861853] [<ffffffff8107e4d1>] worker_thread+0x121/0x3a0
[ 2723.861856] [<ffffffff8107e3b0>] ? manage_workers.isra.23+0x2b0/0x2b0
[ 2723.861859] [<ffffffff81084e60>] kthread+0xc0/0xd0
[ 2723.861863] [<ffffffff81084da0>] ? kthread_create_on_node+0x120/0x120
[ 2723.861866] [<ffffffff814faafc>] ret_from_fork+0x7c/0xb0
[ 2723.861869] [<ffffffff81084da0>] ? kthread_create_on_node+0x120/0x120
[ 2723.861872] BUG: scheduling while atomic: kworker/u9:0/1692/0xffffffff
[ 2723.861873] Modules linked in: hid_magicmouse hidp btusb bnep xt_mac ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter ip_tables x_tables coretemp kvm_intel kvm iTCO_wdt iTCO_vendor_support joydev hid_generic hid_logitech_dj usbhid gpio_ich hid evdev i2c_i801 microcode nvidia(PO) serio_raw lpc_ich snd_hda_codec_realtek snd_ice1724 snd_ak4113 snd_pt2258 snd_ak4114 snd_i2c snd_ice17xx_ak4xxx snd_ak4xxx_adda snd_ac97_codec ac97_bus snd_rawmidi snd_seq_device snd_hda_intel snd_hda_codec atl1 snd_hwdep snd_pcm snd_page_alloc snd_timer snd mii drm soundcore i2c_core shpchp asus_atk0110 intel_agp intel_gtt button processor rfcomm bluetooth rfkill nf_conntrack_ftp nf_conntrack ext4 crc16 mbcache jbd2 sd_mod sr_mod cdrom ata_generic pata_acpi firewire_ohci ata_piix firewire_core
[ 2723.861920] crc_itu_t ahci pata_jmicron libahci libata scsi_mod ehci_pci uhci_hcd ehci_hcd usbcore usb_common [last unloaded: btusb]
[ 2723.861929] CPU: 1 PID: 1692 Comm: kworker/u9:0 Tainted: P W O 3.12.0-1-ARCH #1
[ 2723.861930] Hardware name: System manufacturer P5K/P5K, BIOS 1006 03/05/2008
[ 2723.861935] ffff8801afc944c0 ffff8801a5239d40 ffffffff814ebffb ffff8801a3837000
[ 2723.861938] ffff8801a5239d50 ffffffff814e95a6 ffff8801a5239e58 ffffffff814f15df
[ 2723.861941] 00000000000144c0 ffff8801a5239fd8 ffff8801a5239fd8 00000000000144c0
[ 2723.861945] Call Trace:
[ 2723.861948] [<ffffffff814ebffb>] dump_stack+0x54/0x8d
[ 2723.861951] [<ffffffff814e95a6>] __schedule_bug+0x4d/0x5b
[ 2723.861955] [<ffffffff814f15df>] __schedule+0x93f/0x950
[ 2723.861958] [<ffffffff81016f70>] ? show_stack_log_lvl+0xd0/0x1c0
[ 2723.861962] [<ffffffff81018245>] ? show_stack+0x25/0x50
[ 2723.861965] [<ffffffff8107db4c>] ? process_one_work+0x1ec/0x450
[ 2723.861968] [<ffffffff814f1619>] schedule+0x29/0x70
[ 2723.861971] [<ffffffff8107e578>] worker_thread+0x1c8/0x3a0
[ 2723.861974] [<ffffffff8107e3b0>] ? manage_workers.isra.23+0x2b0/0x2b0
[ 2723.861977] [<ffffffff81084e60>] kthread+0xc0/0xd0
[ 2723.861981] [<ffffffff81084da0>] ? kthread_create_on_node+0x120/0x120
[ 2723.861983] [<ffffffff814faafc>] ret_from_fork+0x7c/0xb0
[ 2723.861987] [<ffffffff81084da0>] ? kthread_create_on_node+0x120/0x120

Has anyone find a fix for this? I've been using my Dragon Dictate headset on my MacBook Pro for about a year, and then today, when I plugged it in, I got this:
4/16/14 10:01:04.000 AM kernel[0]: USBF:    47.766    The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0x4000000)
4/16/14 10:01:07.000 AM kernel[0]: USBF:    50.269    AppleUSBHubPort::FatalError - Port 1 of Hub at 0x4000000 reported error 0xe00002c7 while doing clearing port power feature
4/16/14 10:01:07.000 AM kernel[0]: USBF:    50.269    The IOUSBFamily was not able to enumerate a device.
Here is what I have tried so far:
Reset the PRAM
Reset SMC
Verify disk (there were no problems)
Repair permissions
Boot with an external USB hard drive (which works fine on the "problem" computer) that contained an old SuperDuper clone of my hard drive from several months ago. I received the same "The IOUSBFamily was not able to enumerate a device" error when I plug in the headset.
Tried to headset on another computer, and it worked fine.
Plug in an external USB keyboard into the problem computer, and it works fine.
All of this would lead me to conclude that it is a hardware problem. But it seems that if it were a hardware problem, the external USB keyboard and external USB hard drive would not work (which they do). If the problem were with the headset, it wouldn't work on another computer, but it does. So I'm wondering if it's some sort of firmware issue…??????? URG!!!!!!

BUG: Alt+Scroll to Zoom with 4K Monitor on Windows

Windows 8.1 users with 4K monitors and have Windows' upscaling enabled, please let me know if you can reproduce in the comments! If you have a Mac, you can try to reproduce too, to see if it's just a Windows thing.
I recently setup a 28" 4K monitor for my Windows machine, and upgraded to Windows 8.1, because it has better independent monitor scaling. I also still have a 1920x1080 monitor. (I don't recommend this setup and Windows 8.1 doesn't handle it well. But that's another story)
Premiere Pro is up to date: 2014.2 Release: v8.1, Caravan
By default, Windows has this slider set to the middle recommended setting:
This upscales almost everything seen in Windows, including Premiere Pro's interface.
There's one problem: While hovering over my Timeline, holding down the Alt key and scrolling my mouse wheel doesn't zoom in as it should. It zooms, but the location it zooms into is incorrect.
Here's how Alt+scrolling to zoom usually works:
- wherever your cursor is located is where you zoom in to. If your cursor is hovering over the CTI, you'll zoom in with the CTI centered. If your cursor is at the 2 minute mark, when you alt-scroll to zoom in, the 2 minute mark will be centered in the timeline.
With Windows 8 scaling turned on, the math that drives Alt+scrolling's centering algorithm is totally thrown off! It's hard to describe in words, so here's a graphic that shows exactly what happens when I place my cursor over the red spots and try alt+scrolling:
If the software was working as intended, the red & yellow arrows would overlap eachother, because your zooming should be centered right where the cursor is.
It's driving me crazy, as I rely on the Alt+Scroll method to zoom. Zoom Tool and the +/- keys aren't granular enough; and resizing the horizontal scrollbar is a newer addition to Premiere that I haven't needed to use just yet, as alt+scroll was working fine for me until upgrading to 4K.
Now, I did consider that my second 1080p monitor might have added to the math problems as it has a different amount of scaling applied to it, but I completely disabled the second monitor and ran tests and had the same bug, so the chance of my second monitor having any affect on this bug is incredibly slim.
Obviously there are workarounds:
Turn of the Windows DPI scaling. Fixes the problem instantly, but everything is really tiny on the screen, and isn't really recommended
Don't use the Alt+Scroll method to zoom.
I'm assuming this is only a Windows bug, but if someone wants to test this out on a Mac with a Retina display, that would be helpful!
Can anyone else reproduce this bug? If so, can we all file bug reports to make sure the message gets across? I've heard from Mark that that's the best way to make sure the Premiere team takes an issue seriously. If a bug is only reported by a single user, there's a chance that very few users are encountering the issue, and they won't prioritize a fix.

Hi Tim,
If it's not recommended to use the software when DPI scaling is enabled, it would be nice if the software would give you a one-time warning, letting you know that Premiere Pro hasn't been fully optimized to work properly when scaling is enabled.
Not a bad idea. Would you mind filing a bug report? http://adobe.ly/ReportBug
So, I just installed Premiere Pro the day of this post on a brand new machine. If Caravan isn't the current version, why is Creative Cloud still telling me I'm up to date? I've restarted my computer a few times... the the CC app should know what's apps are up to date and which aren't, correct? Or is it just a mistake that "Caravan" is shown in the about info?
This drives me a little crazy. I will bring this up with my colleagues. The actual version number is at the bottom of the "About Premiere Pro" screen. Because it says 8.1 at the top of the screen is confusing customers.
Another bug at higher DPIs that I noticed after posting this... plugins are cropped wrong. Here's what it looks like if I use a Dynamics effect:
It's annoying, but this one has an easy workaround... just resize the window to way bigger than it should need to be. Sure, the bypass button and presets are partially covered, but it's still usable.
It would be great to get a bug report about that, as well. Thanks!
So yeah, in conclusion:
It would be great if you could let your customers know up-front in the software that Premiere Pro isn't fully ready for Windows' hardware scaling. Photoshop has a HiDPI setting, but the dev team rightfully tucked it away in an experimental features section.
besides these bugs, the software seems to work as intended, so you guys are almost there, thankfully!
Thanks so much for reporting back.
Regards,
Kevin

Bug scale on Mozilla Firefox Windows 8.1

Hello,
I have a strange bug on Mozilla Firefox or in Google Chrome npapi on Windows 8.1, not on Windows XP
ie, Google Chrome ppapi works fine
package{
import flash.display.Sprite;
import flash.events.Event;
import flash.display.StageAlign;
import flash.display.StageScaleMode;
[SWF(width="500", height="500", frameRate="60")]
public class Main extends Sprite{
public function Main(){
stage.align = StageAlign.TOP_LEFT;
stage.scaleMode = StageScaleMode.NO_SCALE;
addEventListener(Event.ADDED_TO_STAGE, init);
private function init(event:Event):void{
removeEventListener(Event.ADDED_TO_STAGE, init);
trace(stage.stageWidth+" "+stage.stageHeight);
var rectangle:Sprite = new Sprite();
rectangle.graphics.beginFill(0xFF0000);
rectangle.graphics.drawRect(0, 0, 1000, 1000);
rectangle.graphics.endFill();
this.addChild(rectangle);
var rectangle2:Sprite = new Sprite();
rectangle2.graphics.beginFill(0x0000FF);
rectangle2.graphics.drawRect(0, 0, 500, 500);
rectangle2.graphics.endFill();
this.addChild(rectangle2);
I have this bug when I compile my swf with Flash Builder, I have the same bug with flash CC
stage.stageWidth, stage.stageHeight return 750 instead of 500
Thanks

Another people have this problem : https://bugbase.adobe.com/index.cfm?event=bug&id=3536168
Ark42 says "Flash works with HiDPI on Windows in Chrome and IE (PPAPI and ActiveX) but not in Firefox (NPAPI). Why does the NPAPI version not get the same fixes? Flash is basically completely unusable on Firefox if you have a 200% scaling setting in Windows, which is common on more and more laptops now."

Index with "or" clause (BUG still exists?)

The change log for 2.3.10 mentions "Fixed a bug that caused incorrect query plans to be generated for predicates that used the "or" operator in conjunction with indexes [#15328]."
But looks like the Bug still exists.
I am listing the steps to-repro. Let me know if i have missed something (or if the bug needs to be fixed)
DATA
dbxml> openContainer test.dbxml
dbxml> getDocuments
2 documents found
dbxml> print
<node><value>a</value></node>
<node><value>b</value></node>
INDEX (just one string equality index on node "value")
dbxml> listIndexes
Index: unique-node-metadata-equality-string for node {http://www.sleepycat.com/2002/dbxml}:name
Index: node-element-equality-string for node {}:value
2 indexes found.
QUERY
setVerbose 2 2
preload test.dbxml
query 'let $temp := fn:compare("test", "test") = 0
let $results := for $i in collection("test.dbxml")
where ($temp or $i/node[value = ("a")])
return $i
return <out>{$temp}{$results}</out>'
When $temp is true i expected the result set to contain both the records, but that was not the case with the index. It works well when there is no index!
Result WITH INDEX
dbxml> print
<out>true<node><value>a</value></node></out>
Result WITHOUT INDEX
dbxml> print
<out>true<node><value>a</value></node><node><value>b</value></node></out>

Hi Vijay,
This is a completely different bug, relating to predicate expressions that do not examine nodes. Please try the following patch, to see if it fixes this bug for you:
--- dbxml-2.3.10-original/dbxml/src/dbxml/optimizer/QueryPlanGenerator.cpp     2007-04-18 10:05:24.000000000 +0100
+++ dbxml-2.3.10/dbxml/src/dbxml/optimizer/QueryPlanGenerator.cpp     2007-08-08 11:32:10.000000000 +0100
@@ -1566,11 +1572,12 @@
     else if(name == Or::name) {
          UnionQP *unionOp = new (&memMgr_) UnionQP(&memMgr_);
+          result.operation = unionOp;
          for(VectorOfASTNodes::iterator i = args.begin(); i != args.end(); ++i) {
               PathResult ret = generate(*i, ids);
               unionOp->addArg(ret.operation);
+               if(ret.operation == 0) result.operation = 0;
-          result.operation = unionOp;
     // These operators use the presence of the node arguments, not their valueJohn

Bug report follow-up

is there a way to follow-up on a bug report that i submitted? i have the bug number, but would like to see if the report was understood, filled out properly and determine the status of the bug report.
thanks,
doug

They comment on bugs if actions were taken. Otherwise - don't expect any feedback.

Solaris8 and 9 (possibly 7) /dev/poll driver bug report.

Hello,
I'd like to report a bug in the solaris 8 and 9 /dev/poll driver (poll(7d)).
As i do not have a support account with sun or anything like that, there
seems to be no other way to do that here (which is of course a very sad
thing).
Bug details:
The /dev/poll device provides an ioctl-request (DP_ISPOLLED) for checking
if a particular filedescriptor is currently in the set of monitored
filedescriptors for that particular /dev/poll fd set (open /dev/poll fd).
A quote from the documentation of the poll(7d) manual page taken from
Solaris9:
"DP_ISPOLLED ioctl allows you to query if a file descriptor is already in
the monitored set represented by fd. The fd field of the pollfd structure
indicates the file descriptor of interest. The DP_ISPOLLED ioctl returns 1
if the file descriptor is in the set. The events field contains the
currently polled events. The revents field contains 0. The ioctl returns 0
if the file descriptor is not in the set. The pollfd structure pointed by
pfd is not modified. The ioctl returns a -1 if the call fails."
It says that when you query for an filedescriptor which is currently being
monitored in the set, that it would return 1, and change the events field of
the pollfd structure to the events it's currently monitoring that fd for.
The revents field would be set to zero.
However the only thing which actually happens here, is that FD_ISPOLLED
returns 1 when the fd is in the set and 0 if not. When the fd is in the
set, when FD_ISPOLLED returns 1, the events field remains unmodified, but
the revents field gets changed.
A small sample code to illustrate:
#include <stdio.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <sys/devpoll.h>
main() {
struct pollfd a;
int dp_fd = open("/dev/poll", O_WRONLY);
a.fd = 0; /* stdin */
a.events = POLLIN; /* we monitor for readability, POLLIN=1 */
a.revents = 0;
write(dp_fd, &a, sizeof(a));
a.fd = 0;
a.events = 34; /* filled in with bogus number to show malfunctioning */
a.revents = 0;
printf("DP_ISPOLLED returns: %d\n", ioctl(dp_fd, DP_ISPOLLED, &a));
printf("a.fd=%d, a.events=%hd, a.revents=%hd\n", a.fd, a.events,
a.revents);
According to the documentation of /dev/poll and namely DP_ISPOLLED this
program is supposed to print the following:
DP_ISPOLLED returns: 1
a.fd=0, a.events=1, a.revents=0
However it prints the following:
DP_ISPOLLED returns: 1
a.fd=0, a.events=34, a.revents=1
You can take any number instead of '34' and it will simply remain untouched
after the DP_ISPOLLED ioctl-request.
I hope it's clear now that the solaris8 and solaris9 (and probably solaris7
with /dev/poll patch too) DP_ISPOLLED implementation is broken.
This bug is also easily illustrated by looking at the solaris8 kernel sourcecode:
<snippet osnet_volume/usr/src/uts/common/io/devpoll.c:dpioctl()>
case DP_ISPOLLED:
pollfd_t pollfd;
polldat_t *pdp;
if (pollfd.fd < 0) {
mutex_exit(&pcp->pc_lock);
break;
pdp = pcache_lookup_fd(pcp, pollfd.fd);
if ((pdp != NULL) && (pdp->pd_fd == pollfd.fd) &&
(pdp->pd_fp != NULL)) {
pollfd.revents = pdp->pd_events;
if (copyout(&pollfd, (caddr_t)arg,
sizeof(pollfd_t))) {
mutex_exit(&pcp->pc_lock);
DP_REFRELE(dpep);
return (set_errno(EFAULT));
*rvalp = 1;
</snippet>
its' clearly visible that the code writes the current monitored events to
the revents field:
'pollfd.revents = pdp->pd_events;'
and that it doesnt set revents to zero.
It's funny to see that this has been like this since Solaris8 (possibly 7). That means nobody ever used DP_ISPOLLED that way or people were simply to lazy to file a bug report.
Another funny thing related to this. is that Hewlett-Packard did seem to know about this. Since HP-UX11i version 1.6 they also support /dev/poll. From their manual page i ll quote some sentences from their WARNING session:
"The ioctl(DP_ISPOLLED) system call also returns its result in the revents member of the pollfd structure, in order to be compatible with the implementation of the /dev/poll driver by some other vendors."
Hopefully this will get fixed.
I also like to reexpress my very negative feelings towards the fact that you're not able to file bug reports when you do not have a support contract. Ridiculous.
Thanks,
bighawk

Have I mentioned how much i love my playbook now Great job on os 2.0

[bdb bug]repeatly open and close db may cause memory leak

my test code is very simple :
char *filename = "xxx.db";
char *dbname = "xxx";
for( ; ;)
DB *dbp;
DB_TXN *txnp;
db_create(&dbp,dbenvp, 0);
dbenvp->txn_begin(dbenvp, NULL, &txnp, 0);
ret = dbp->open(dbp, txnp, filename, dbname, DB_BTREE, DB_CREATE, 0);
if(ret != 0)
printf("failed to open db:%s\n",db_strerror(ret));
return 0;
txnp->commit(txnp, 0);
dbp->close(dbp, DB_NOSYNC);
I try to run my test program for a long time opening and closing db repeatly, then use the PS command and find the RSS is increasing slowly:
ps -va
PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND
1986 pts/0 S 0:00 466 588 4999 980 0.3 -bash
2615 pts/0 R 0:01 588 2 5141 2500 0.9 ./test
after a few minutes：
ps -va
PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND
1986 pts/0 S 0:00 473 588 4999 976 0.3 -bash
2615 pts/0 R 30:02 689 2 156561 117892 46.2 ./test
I had read bdb's source code before, so i tried to debug it for about a week and found something like a bug:
If open a db with both filename and dbname, bdb will open a db handle for master db and a db handle for subdb,
both of the two handle will get an fileid by a internal api called __dbreg_get_id, however, just the subdb's id will be
return to bdb's log region by calling __dbreg_pop_id. It leads to a id leak if I tried to open and close the db
repeatly, as a result， __dbreg_add_dbentry will call realloc repeatly to enlarge the dbentry area, this seens to be
the reason for RSS increasing.
Is it not a BUG?
sorry for my pool english :)
Edited by: user9222236 on 2010-2-25 下午10:38

I have tested my program using Oracle Berkeley DB release 4.8.26 and 4.7.25 in redhat 9.0 (Kernel 2.4.20-8smp on an i686) and AIX Version 5.
The problem is easy to be reproduced by calling the open method of db handle with both filename and dbname being specified and calling the close method.
My program is very simple:
#include <stdlib.h>
#include <stdio.h>
#include <sys/time.h>
#include "db.h"
int main(int argc, char * argv[])
int ret, count;
DB_ENV *dbenvp;
char * filename = "test.dbf";
char * dbname = "test";
db_env_create(&dbenvp, 0);
dbenvp->open(dbenvp, "/home/bdb/code/test/env",DB_CREATE|DB_INIT_LOCK|DB_INIT_LOG|DB_INIT_TXN|DB_INIT_MPOOL, 0);
for(count = 0 ; count < 10000000 ; count++)
DB *dbp;
DB_TXN *txnp;
db_create(&dbp,dbenvp, 0);
dbenvp->txn_begin(dbenvp, NULL, &txnp, 0);
ret = dbp->open(dbp, txnp, filename, dbname, DB_BTREE, DB_CREATE, 0);
if(ret != 0)
printf("failed to open db:%s\n",db_strerror(ret));
return 0;
txnp->commit(txnp, 0);
dbp->close(dbp, DB_NOSYNC);
dbenvp->close(dbenvp, 0);
return 0;
DB_CONFIG is like below:
set_cachesize 0 20000 0
set_flags db_auto_commit
set_flags db_txn_nosync
set_flags db_log_inmemory
set_lk_detect db_lock_minlocks
Edited by: user9222236 on 2010-2-28 下午5:42
Edited by: user9222236 on 2010-2-28 下午5:45

Multiple return values (Bug-ID 4222792)

I had exactly the same request for the same 3 reasons: strong type safety and code correctness verification at compile-time, code readability and ease of mantenance, performance.
Here is what Sun replied to me:
Autoboxing and varargs are provided as part of
JSRs 14 and 201
http://jcp.org/en/jsr/detail?id=14
http://jcp.org/en/jsr/detail?id=201
See also:
http://forum.java.sun.com/forum.jsp?forum=316
http://developer.java.sun.com/developer/earlyAccess/adding_generics/index.html
Multiple return values is covered by Bug-ID 4222792
Typically this is done by returning an array.
http://developer.java.sun.com/developer/bugParade/bugs/4222792.html
That's exactly the problem: we dynamically create instances of array objects that would better fit well within the operand stack without stressing the garbage collector with temporary Array object instances (and with their backing store: 2 separate allocations that need to be recycled when it is clearly a pollution that the operand stack would clean up more efficiently)
If you would like to engage in a discussion with the Java Language developers, the Generics forum would be a better place:
http://forum.java.sun.com/forum.jsp?forum=316
I know that (my report was already refering to the JSR for language extension) Generics is not what I was refering to (even if a generic could handle multiple return values, it would still be an allocated Object
instance to pack them, i.e. just less convenient than using a static class for type safety.
The most common case of multiple return values involve values that have known static datatypes and that should be checked with strong typesafety.
The simple case that involves returning two ints then will require at least two object instances and will not solve the garbage collection overhead.
Using a array of variable objects is exactly similar, except that it requires two instances for the components and one instance for the generic array container. Using extra method parameters with Integer, Byte, ... boxing objects is more efficient, but for now the only practical solution (which causes the least pollution in the VM allocator and garbage collector) is to use a custom class to store the return values in a single instance.
This is not natural, and needlessly complexifies many interfaces.
So to avoid this pollution, some solutions are used such as packing two ints into a long and returning a long, depacking the long after return (not quite clean but still much faster at run-time for methods that need to be used with high frequencies within the application. In some case, the only way to cut down the overhead is to inline methods within the caller code, and this does not help code maintenance by splitting the implementation into small methods (something that C++ can do very easily, both because it supports native types parameters by reference, and because it also supports inline methods).
Finally, suppose we don't want to use tricky code, difficult to maintain, then we'll have to use boxing Object types to allow passing arguments by reference. Shamely boxed native types cannot be allocated on the operand stack as local variables, so we need to instanciate these local variables before call, and we loose the capacity to track the cases where these local variables are not really initialized by an effective call to the method that will assign them. This does not help debugging, and is against the concept of a strongly typed language like Java should be:
Java makes lots of efforts to track uninitialized variables, but has no way to determine if an already instanciated Object instance refered in a local variable has effectively received an effective assignment because only the instanciation is kept. A typical code will then need to be written like this:
Integer a = null;
Integer b = null;
if (some condition) {
//call.method(a, b, 0, 1, "dummy input arg");
// the method is supposed to have assigned a value to a and b,
// but can't if a and b have not been instanciated, so we perform:
call.method(a = new Integer(), b = new Integer(), 0, 1, "dummy input
arg");
// we must suppose that the method has modified (not initialized!)
the value
// of a and b instances.
now.use(a.value(), b.value())
// are we sure here that a and b have received a value????
// the code may be detected at run-time (a null exception)
// or completely undetected (the method() above was called but it
// forgot to assign a value to its referenced objects a and b, in which
// case we are calling in fact: now.use(0, 0); with the default values
// or a and b, assigned when they were instanciated)
Very tricky... Hard to debug. It would be much simpler if we just used:
int a;
int b;
if (some condition) {
(a, b) = call.method(0, 1, "dummy input arg");
now.use(a, b);
The compiler would immediately detect the case where a and b are in fact not always initialized (possible use bere initialization), and the first invoked call.method() would not have to check if its arguments are not null, it would not compile if it forgets to return two values in some code path...
There's no need to provide extra boxing objects in the source as well as at run-time, and there's no stress added to the VM allocator or garbage collector simply because return values are only allocated on the perand stack by the caller, directly instanciated within the callee which MUST (checked at compile-time) create such instances by using the return statement to instanciate them, and the caller now just needs to use directly the variables which were referenced before call (here a and b). Clean and mean. And it allows strong typechecking as well (so this is a real help for programmers.
Note that the signature of the method() above is:
class call {
(int, int) method(int, int, String) { ... }
id est:
class "call", member name "method", member type "(IILjava.lang.string;)II"
This last signature means that the method can only be called by returning the value into a pair of variables of type int, or using the return value as a pair of actual arguments for another method call such as:
call.method(call.method("dummy input arg"), "other dummy input arg")
This is strongly typed and convenient to write and debug and very efficient at run-time...

Can anyone give me some real-world examples where
multiple return values aren't better captured in a
class that logically groups those values? I can of
course give hundreds of examples for why it's better
to capture method arguments as multiple values instead
of as one "logical object", but whenever I've hankered
for multiple return values, I end up rethinking my
strategy and rewriting my code to be better Object
Oriented.I'd personally say you're usually right. There's almost always a O-O way of avoiding the situation.
Sometimes though, you really do just want to return "two ints" from a function. There's no logical object you can think of to put them in. So you end up polluting the namespace:
public class MyUsefulClass {
public TwoInts calculateSomething(int a, int b, int c) {
public static class TwoInts {
    //now, do I use two public int fields here, making it
    //in essence a struct?
   //or do I make my two ints private & final, which
   //requires a constructor & two getters?
//and while I'm at it, is it worth implementing
//equals(), how about hashCode()? clone()?
//readResolve() ?
}The answer to most of the questions for something as simple as "TwoInts" is usually "no: its not worth implementing those methods", but I still have to think about them.
More to the point, the TwoInts class looks so ugly polluting the top level namespace like that, MyUsefulClass.TwoInts is public, that I don't think I've ever actually created that class. I always find some way to avoid it, even if the workaround is just as ugly.
For myself, I'd like to see some simple pass-by-value "Tuple" type. My fear is it'd be abused as a way for lazy programmers to avoid creating objects when they should have a logical type for readability & maintainability.
Anyone who has maintained code where someone has passed in all their arguments as (mutable!) Maps, Collections and/or Arrays and "returned" values by mutating those structures knows what a nightmare it can be. Which I suppose is an argument that cuts both ways: on the one hand you can say: "why add Tuples which would be another easy thing to abuse", on the other: "why not add Tuples, given Arrays and the Collections framework already allow bad programmers to produce unmainable mush. One more feature isn't going to make a difference either way".
Ho hum.

Extensions like Ghostery, WOT or AdBlock stop working after two or three times. Restarting the webpage in a new tab the extensions will work again for several times and then stop again. Has anybody an explanation or a workaround for this bug in Safari 5?

Extensions like Ghostery, WOT or AdBlock stop working after two or three times. Restarting the webpage in a new tab the extensions will work again for several times and then stop again. Has anybody an explanation or a workaround for this bug in Safari 5?

Remove the extensions, redownload Safari, reload the extensions.
http://www.apple.com/safari/download/
And if you really want a better experience, use Firefox, tons more choices and possibilities there.
Firefox's "NoScript" will block the Trojan going around on websites. Best web security you can get.
https://addons.mozilla.org/en-US/firefox/addon/noscript/
Ghostery, Ad Block Plus and thousands of add-ons more have originated on Firefox.

Bug? My events on the iPad iCal app aren't shown in the year view if they are more than two years in the future.

My events on the iPad iCal app aren't shown in the year view if they are more than two years in the future even though I can see them on the month, week and day view. Any suggestions on how to fix it? I've tried it all. I called the apple support and they checked on their iPads. They all did the same and they couldn't help me. They suggested trying this way. I'd like to be able to plan a few years ahead and the year view would make thing so easy!
Is this a bug?

Go to the Home screen and double click the Home button. That will reveal the row of recently used apps at the bottom of the screen. Tap and hold on the app in question until it wiggles and displays a minus sign. Tap the minus sign to actually quit the app. Then tap anywhere on the screen above that bottom row to return the screen to normal. Then restart the app and see if it works normally.
Then reboot your iPad. Press and hold the Home and Sleep buttons simultaneously ignoring the red slider until the Apple logo appears. Let go of the buttons and let the iPad restart. See if that fixes your problem.

HT4528 My IPhone Bugged out/It is currently in the reset mode. I need to exchange all of my contacts from my Yahoo acct. to my new IPHONE. Can you please help me?

Hello ,
I purchased my IPHONE about 2 months ago. I am visiting family in DE & this tuesday it starting to go off & on by itself. Then the icons looked like they were floating . Then I could not call or text . The SIRI device would not work. Then it would shut down then the apple icon would reappear. I took it to a verizon dealer in Rehoboth DE & they said it BUGGED OUT/It is in a RESTORE MODE. It will not turn on. We could not transfer anny of my pics or contacts. I never even had a chance to back up the memory on ITUNES.
The tech @ Verizon said to contact APPLE to trouble shoot and try and transfer the contacts from my yahoo acct.
Can you please help?
Gina

set up your yahoo account in mail, contacts, calendars as an Exchange Account and you should be able to get your contacts from Yahoo from there.

ICal bug!

Didn't know where to post it so I decided to post it here. Not a major bug, but a bug nevertheless. Maybe someone here wants to check it out on their iCal so I get a sense if it is touching just me or anyone else.
Follow all steps:
- open iCal in weekly view.
- click on a day differen than "today".
- click on "today" on the upper left side (where "today" is written ).
- click on the red dot to "close the app" without really closing it.
- reopen iCal by clicking on the icon.
Now you should have the today button greyed out, no matter which day you choose. The only way to have it back is to close and reopen iCal.
No data loss, nothing... Just a little bug I found in iCal.
I run Mac OSX 10.5.4 on a MacBook Pro 17" no plugins, nothing installed. Software is in italian.
Anyway: others get the same result? (just checked it again to be really sure it is indeed not working, and it's not..)

Has a real solution to this bug been found yet? It has been on going for me and has become annoying. The only way to get the "today" button and the search feature to work, is to quit iCal and start it again.
Very annoying.

Okay, the iTunes 8.2 bug that I had on my iPod Touch is back with my iPhone

I have new iPhone 3GS that I picked up this morning at 7 am. I love it, but the iTunes 8.2 bug that is being thoroughly discussed in the iPod Touch forum is back and affecting my iPhone 3GS. I did read one random post that a Apple Tech Support person said to unplug the internet (disconnect your internet) before plugging it in. I don't know why, but it worked and makes me wonder if this will also work for iPod Touch users. Weird, but it is definitely a nice work around for now!

I got it again. I plug in the iPhone into my computer and it is telling that it thinks it is a camera because it is trying to launch Canon CameraWindow, MS scanner, Picasa3, etc. Then iTunes says, "An iPhone has been detected, but it could not be identified properly. Please, disconnect and reconnect the iPhone, then try again." Yes, I tried again, and completely uninstalled iTunes and all things Apple to only re-install it. I am at my whits end again!

IOS 8 - Photos app bug - "stuttering" effect on Year view

Hi Folks,
On the iPhone6 Plus 128GB with iOS8.1.3 (with 15000 photos inside several years go), I notice that when using the Photos native app in the “Year view” (yearly mosaic view), if I scroll up or down slightly fast, the scrolling that you get has a little “stuttering” or “jerking” effect, so the UI is not perfectly smooth in this view inside Photos native app.
Have you noticed it in your own iPhone's with iOS8.1.3. and also having a huge size photo callery as I have (>10000 photos spread in several years)? (I think that is it very important, because if you have not a huge photo gallery, probably you will not see the “stuttering” or “jerking” effect that I am describing).
I think this is a bug which impacts iOS User eXperience, which needs to be fixed.
Thanks by your feedback!

Hi Guys!
Any experience to share with us, please?
Thanks!

Hidpi Bug ??????

Similar Messages

Maybe you are looking for